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.
Thread beginning with comment 552446
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[10]: Comment by ssokolow
by cdude on Thu 14th Feb 2013 15:21 UTC in reply to "RE[9]: Comment by ssokolow"
cdude
Member since:
2008-09-21

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


And how would that be different with n completely different rendering-engines? I will tell you: since WebKit is LGPL all the work done on WebKit is open sourced and so everybody can use, can upgrade, can move on to invent in the WebKit world.

See what Opera just did and why they did. They will now be closer to the web, have a lesser fragmented web, incooperate changew like fixes or new features faster, improve compatibility. How would that be better with sticking with Presto? It wouldn't.

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.


They are using V8. In reality WebKit has only 2 Javascript engines. Those JavascriptCore based on KJS and V8. Opera picked V8.


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


No, its WebCore plus glue. Still the same.


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


How evil!!!1!


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.


I don't know when you tried last but since some years there is no difference except for maybe fonts depending on the OS.


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.


No shit sherlock. Metro doesn't use WebKit? That's an agument contra WebKit! Come on.

QML isn't a browser neither is GTK.


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


No, it isn't a browser but "WebKit is an open source web browser engine." - from webkit.org

Reply Parent Score: 3

RE[11]: Comment by ssokolow
by moondevil on Thu 14th Feb 2013 15:32 in reply to "RE[10]: Comment by ssokolow"
moondevil Member since:
2005-07-08

And how would that be different with n completely different rendering-engines? I will tell you: since WebKit is LGPL all the work done on WebKit is open sourced and so everybody can use, can upgrade, can move on to invent in the WebKit world.


Really?!

http://blog.methvin.com/2013/02/tragedy-of-webkit-commons.html

No, it isn't a browser but "WebKit is an open source web browser engine." - from webkit.org


Which happens to be a different version in every browser.

Edited 2013-02-14 15:38 UTC

Reply Parent Score: 3

RE[12]: Comment by ssokolow
by cdude on Thu 14th Feb 2013 23:56 in reply to "RE[11]: Comment by ssokolow"
cdude Member since:
2008-09-21

really?


Yes, really! Your link confirms that. Opera just came in and improved WebKit and now all WebKit based browsers including Opera will profit. Easy!

Reply Parent Score: 2

RE[11]: Comment by ssokolow
by lucas_maximus on Thu 14th Feb 2013 16:04 in reply to "RE[10]: Comment by ssokolow"
lucas_maximus Member since:
2009-08-18

Somebody doesn't know what they are talking about on here again.

Webkit is a not a browser, there will different versions of webkit shipped with different browser versions. Some of those browser versions will get updated quicker and older versions will be dropped quicker than others.

Luckily the jQuery team do most of the cross browser shims for me.

Edited 2013-02-14 16:17 UTC

Reply Parent Score: 3

RE[12]: Comment by ssokolow
by cdude on Thu 14th Feb 2013 23:59 in reply to "RE[11]: Comment by ssokolow"
cdude Member since:
2008-09-21

Somebody doesn't know what they are talking about on here again.


No problem. We will solve your confusion :-)


Webkit is a not a browser


No, its a browser engine. See the, my, comment you just replied too. I even gave a source just for you. Its that link, click it, read it and your confusion is gone.

Reply Parent Score: 1