Kimmo Kinnunen wrote yesterday on the GTK+-WebCore developer mailing list that he has imported the Safari 2.0 WebCore branch into GTK+-WebCore. "This means that from the webcore/javascriptcore part, the code is mostly
the same as in current Safari. So if there are any crashes, they're not
from webcore/javascriptcore part of the codebase with very high
probability, rather my code."
To read all comments associated with this story, please click here.
Member since:2005-07-06
Why should they do that? Opera already has a better renderer than KTHML/WebCore/Safari.
It would make no sense for them to adopt an inferior one.
Member since:2005-11-10
It would if they want their market share to go above 1%. Web developers have to deal all the quirks of Trident, Gecko and possibly KHTML/WebKit if they have access to it; debugging for Presto (Opera) on top of that to (with yet another JavaScript engine as well) is not worth the effort for minimal gains in users. Not even Prototype support Opera officially, they have too much hacking on their hands as it is.
Member since:2005-10-02
LOL
Opera is almost as bad as Firefox and Gecko. Opera is slow, bloated, unstable and extremely memoryhungry. I tried to replace Firefox with Opera, but the slowness, the lack of stability, the memory consumption and lack of - for me - useful extensions meant I left it behind.
It has a reasonable renderer but it is no match for WebCore/KHTML.
I'm looking forward to Epiphany on GTK+-WebCore.
Member since:
2005-11-10
The less rendering engines (less browsers doesn't matter) I have to debug for, the better. Now if only Opera would adopt KHTML...