Linked by Thom Holwerda on Wed 13th Feb 2013 13:21 UTC
Opera Software De kogel is door de kerk: as we already talked about earlier, Opera is going to switch to the WebKit engine, leaving its own Presto rendering engine behind. We didn't yet know if they would the switch only on mobile or on the desktop as well, and they cleared that up too: both mobile and desktop Opera Browsers will switch to the WebKit rendering engine.
Permalink for comment 552438
To read all comments associated with this story, please click here.
RE[9]: Comment by ssokolow
by lucas_maximus on Thu 14th Feb 2013 11:17 UTC in reply to "RE[8]: Comment by ssokolow"
Member since:

I don't really understand what you are complaining about or indeed what you want to happen instead.

No obviously you don't.

You don't seem to care about there are thousands of incompatible forks of webkit that all implement the standards incorrectly.

Also this says nothing about the JavaScript interpreters which there are more than 6 or 7 different interpreter in the wild, which aren't tied to the Webkit engine.

Let alone all the application frameworks that are using (incompatible) versions of Webkit (SmartTV SDK versions on its own is different enough).

Then we have even in the same browser version on different operating systems.

Safari (last time I checked) works differently on Windows than it does on MacOSX and probably works differently on iOS ... that is fragmentation in the same bloody code base.

Then we have projects that want to start using HTML 5 and JS in their desktop frameworks (QML, Metro, GTK), which won't be webkit.

So instead of having a nice set of reusable tools that I could use on any project that is HTML and JS, I have to a slight hack for each platform.

Webkit isn't a browser, it is just one component of. Much like Linux is one component of a Linux distro.

History is repeating itself again, but it okay this time because Microsoft doesn't come out on top.

Edited 2013-02-14 11:27 UTC

Reply Parent Score: 2