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 view parent comment, click here.
To read all comments associated with this story, please click here.
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-09-14
That may be true, but I've been using Opera for a while, and I don't think they're too worried about desktop market share, to be honest.
They'll take it, but from what I've seen they're more focused on phones and PDAs, which is where they actually make money. The desktop browser is still great and it gets a lot of their attention, but they're just not too concerned about taking market share from the other desktop browsers
Besides that, there's not too much hacking needed to get pages working in Opera. If a page works in Firefox, and passes validation, it usually works in Opera with minimal hacking.
But that's just my experience, and I'm a big Opera fan, so I'm a little biased.
Edited 2007-04-07 13:28
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:2006-04-26
What exactly do you see as "extremely memoryhungry" in Opera!? And what is slow? For me it is the other way around. Firefox is slower and uses more memory, even without useful extensions installed. Ok, not that much, only 10 MB. Subjective speed seems to me at least double in Opera in startup and rendering of most sites compared against a bare Firefox. Stability? No real concern. It doesn't crash that often. Maybe this is a question of general System setup?
Edited 2007-04-07 12:48
Member since:2005-07-06
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.
I suppose you can prove all of this too with hard facts? Sorry, but Opera is anything has a reputation for being fast, not bloated, and NOT memory hungry. Whereas FireFox has a reputation for being slow, bloated, and memory hungry. A *provable* one as well. Didn't see you see Thom's post a few months ago about constant problems with FireFox and how he started using Opera instead?
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.