OmniWeb Announces 5.0 Browser
wcbrown writes "OmniGroup, makers of the popular Mac OS X browser OmniWeb have announced the upcoming beta of their next-generation browser. There's going to be tabs and they're not like any other browser out there. There's going to be a way to save and share your browsing state so you can restore your window locations and the URLs in them. There's going to be some cool nice-to-haves like integrated RSS reading, per-site preferences, and search shortcuts. The beta will be available February 2, 2004."
They look quite weak from that video. They aren't nearly as useful as regular tabs (a la Mozilla, Safari et. al), as a matter of fact Omni's take on "tabs" reminds me of a glorified "Page Holder" from IE 5 for Mac OS 9. My real question is what does OmniWeb have to offer? It's using Apple's WebKit last time I checked, so it's not a new rendering engine that they have to give, no *REAL* tabbed browsing (which is what I want) so no dice there. I understand more choices are good yadda yadda yadda and all that jazz, but my question still stands, what does OmniWeb have to offer the end user?
Are you secure enough in your masculinity to run 'man touch'?
Apple does seem to have gotten sloppy with terminology once again. They can't call a component "JavaScriptCore" -- technically and legally, "JavaScript" can only describe the Netscape implementation of the language. The generic term is ECMAScript. Anyone taking bets on how long before Time-Warner's lawyers notice the trademark infringment?
There's a lesson here for those of us stuck with Gecko, Opera, or the mysterious combination of undocumented engines that is Internet Explorer. You want standardization, you gotta have open-source components. W3C puts a lot of work in defining standards for HTML, CSS, and SVG. These standards have a lot of unbelievably cool features, with much more in the pipe. But nobody can use most of them, because they're not widely implemented. What's the point of working so hard to create good standards if nobody uses them?
We need a reference web engine that will drive standards-based web development, just as the reference implementation of Java, with all its flaws, drove the adoption of the Java platform. Microsoft probably wouldn't use it, but it would provide some small pressure for them to be more standards compliant. W3C could develop such a comonent from scratch, or they could use Gecko; but KHTML seems to have the code base that's closest to a real tipping point.
My three reasons for sticking with Safari are:
1) The Google Toolbar (although not implemented in the same full and correct way as the real thing on Windows).
2) Ad blocking
3) Pith Helmet - it allows ad content (or really any content) in a web page to be blocked. So banners and images can be stopped and not downloaded - saving my slow connection from having to bother with them, as well as not even seeing the ads.
I also like the bookmark bar, but I suppose many of the browsers have that now.
I know little to nothing about OmniWeb, will have to check it out more.
There are some odd things afoot now, in the Villa Straylight.
My impression is that usually the opposite is true, since screens are wider than they are tall, especially with the proliferation of widescreen aspect ratios.
... I'm still looking forward to giving it a try.
It's a side effect of having a wide screen. Because my (PowerBook 15") screen is wider than it is tall, on average, each individual window takes up all the vertical space (or at least, enough so that I can't have another usable window in the same x coordinates). There is additional space above and below the window, but not enough for another usable window.
So, if I need to use two windows at once, I need to put them next to each other (or change their size, which is too time-consuming). If I keep my browser windows the same size as I normally do, OmniWeb windows will take up a lot more of my usable space, not just because they take up more space (they do) but because they take up the space I am actually using for something else, whereas adding a horizontal bar takes up more vertical space, which wasn't being used for anything anyway. Maybe I shrink the height of my browser windows a dozen or so pixels, but that is insignificant compared to having two windows side-by-side.
And while I am sure I can close the Tabs drawer, I don't want to. I like leaving my list of tabs open. Opening and closing it when going back and forth between windows would be annoying, too.
Me too!
At least in early versions, OmniWeb tried using a 'pure' object-oriented approach to render web pages. They wrote an object that converted HTML into SGML, then another one to convert SGML into RTF -- which was a native format for NextStep to display. Although elegant in architecture, these many conversions delayed the display of the web page quite a bit.
To make matters worse, until OS4.2, the low-level Next-supplied Text Object was not multi-threaded. (No real reason for it to be, until web browsers came along opening up multiple http connections and wanting their pages rendered ASAP.)
I believe if you get just the right combination of OpenStep 4.2 on a Turbo Cube, some rare EOF patch, and the right beta of OmniWeb, the whole rube goldberg contraption works just dandy. Otherwise, it's probably a good thing they are just outsourcing HTML rendering to WebCore nowadays.
There's some more info in an old post of mine here.