![]() Omni are much safer in the long run by using KHTML. They don’t have the resources of Opera, and there’s nothing stopping Opera from terminating Omni Group’s license to use their HTML engine. Once Opera does start to compete, the Omni Group are toast. Opera can’t afford to ignore a market like the growing Mac platform. Opera for Mac OS X may not be very good now, but it will get better. It is designed to be highly functional, and like OmniWeb people are willing to pay for it. In other words, it doesn’t compete with OmniWeb. Safari has a clear design intention: it is meant to be simple and easy to use. The Windows Subsystem for Linux, which is being upgraded to Ubuntu 16.04 LTS in an upcoming Windows 10 update, is designed to ‘run native Linux command-line tools directly on Windows, alongside your traditional Windows desktop and modern store apps.’ But with a bit of technical tinkering and know-how it can run full-blown GUI apps, too. Furthermore, how will OmniWeb distinguish itself if it’s using the same rendering engine as Safari? Who will bother paying for OmniWeb?” (That new operating system, OS X - that's 10, not 'X' - is a powerful argument in favor of buying a new iMac or regular Macintosh.) I like OmniWeb so much that I bought it. Netscape 4, Camino, Galeon, Konqueror, Omniweb, Safari avant la version 1.2, Opera Windows/Linux avant la version 7 ne gèrent pas les raccourcis claviers. A browser I've become very fond of is OmniWeb, available only for the new Mac operating system. If I were Opera, I would greatly enjoy letting someone else market my rendering engine on MacOS X. Netscape 4, Camino, Galeon, Konqueror, Omniweb, Safari before version 1.2 and Opera Windows /Linux before version 7 do not handle keyboard shortcuts. OmniWeb has garnered a following, and currently its only drawback is the rendering engine. PS: to the person who was complaining that Omniweb didn't save your window sizes, go to Browser->Save Window Size and you're set.“ Opera has been a dismal failure on MacOS. i'd like to see full CSS2, and more multithreading (less of the spinning colour wheel), but it's still leaps and bounds better than IE. of course, IE can't seem to do this either, but that doesn't make it ok View image: /infopop/emoticons/icon_smile.gif.īut apart from a few minor issues, Omniweb is great. i don't use Java much, but sometimes i like to play some of 's online games and Omniweb can't handle it. The other thing that it's missing is good Java support. i haven't figured out what pages, or in what combination makes this happen, and it is by far the most annoying bug. The problems? well as some have reported already every once in a while it'll start loading a page and then just sit there with the spinning colour wheel, requiring a force-quit. i also like the spell checking in text boxes like this one View image: /infopop/emoticons/icon_wink.gif. the anti-aliasing looks great (as it's done in Quartz) and i find the page rendering to be extremely fast. I use OmniWeb as my primary browser and i love it. ![]() ![]() even when its locked up like that, i can still move the browser windows around. ![]() It goes into a nonending Spinning Beachball of death, requiring a force quit. OW browser windows don't remeber the size of the windows if you quit and restart it. OW's support for Flash is sub-par, but Internet Explorer's isn't much better, IMHO. Perhaps this is because the Cocoa API is more mature than Carbon and its easier to multithread? Even when its churning away downloading and rendering a page, i can select menu items, minimize the browser, and move browser windows around. I like OmniWeb because its more heavily multithreaded than Internet Explorer. Its that the developers haven't done all they could have. Its not that the OS is slow, necessarily. Carbon developers (including Apple for their Finder and Microsoft for Internet Explorer) don't know how to write good Carbon code that's properly multithreaded. I hear alot of people complaining that this problem is because IE is Carbon based instead of Cocoa, but its not entirely the fault of the APIs. you can't click a link, you can't scroll the current browser, you can't even select any of the menus. When its loading certain larger page, it goes into the spinning color beachball routine and everything is frozen until its done with that page. IE 5.1 doesn't know how to chew gum and walk many times. I have 56K and it takes a while to request, download, and build pages because of the modem sometimes. There is one important reason why I switched to OW as my primary browser over IE 5.1: MULTITHREADING
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |