Next OmniWeb to be based on Safari Engine?

An anonymous reader writes "A MacFixIt article includes a quote from the Omni Group's CEO Ken Case: 'The wonderful news for OmniWeb is that Apple has based it on a fast, compatible (and small!) rendering engine which is tuned for Mac OS X, and which they are making available to the entire Mac OS X development community! [...] This means that we may be able to reach our compatibility and speed goals for OmniWeb much more quickly than when we were working alone, and then return our focus to doing what we do best: providing a rich browsing experience. Thank you, Apple!'"

Comments

Re:WebCore

[Phroggy]

It seems to me that there are two reasons for tabbed browsing:

1) to compensate for poor window navigation - it's too hard to keep track of and switch between open windows, so we use tabs, instead of trying to fix the operating system (window manager) so we don't have this problem across other applications. It's hard to switch between multiple windows in a word processor or spreadsheet app too, but the workaround only exists in some browsers.

2) opening a new tab is far faster than opening a new window. I can only assume this is because the code to open a new window isn't optimized for speed, while the code for opening a new tab within an existing window is, and since the developers use tabs, this won't change.

That said, I'm using tabs in Mozilla right now, because of these reasons.

I hate to say this, but I won't be surprised if Microsoft gets it right in the next version of Windows. XP is already working on addressing this issue, although from what I've seen so far it's not there yet.