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 552418
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Comment by ssokolow
by moondevil on Thu 14th Feb 2013 06:23 UTC in reply to "RE[4]: Comment by ssokolow"
moondevil
Member since:
2005-07-08

Now compare that to Webkit, which is open and non-proprietary. Both the most important companies driving webkit development, Google and Apple, want an open standards based feature rich web, although both want that for different reasons. They don't want that because they are kind of heart, they want that because an open standards based feature rich web enhances and synegises with both their (different) core business models.

I think it is unlikely that webkit will go the way of IE.


I desire that everyone that states this does a contract with a Fortune 500 company to support Webkit across all major operating systems and mobile devices.

Then watch how Webkit being open solves their issues when CSS or JavaScript break across Webkit versions.

Finally have fun discussing compromise solutions on such issues with their project manager.

Reply Parent Score: 3

RE[6]: Comment by ssokolow
by cdude on Thu 14th Feb 2013 15:01 in reply to "RE[5]: Comment by ssokolow"
cdude Member since:
2008-09-21


Then watch how Webkit being open solves their issues when CSS or JavaScript break across Webkit versions.


You not develop against a certain version and vendor but the standard. If behavior/layout changes in WebKit then that happens cause the previous implementation had bugs that got fixed.

Yes, this is a very different approach then what Microsoft does with IE.

As web-developer I thank WebKit for continues fixing and improving the Web at an incredible speed. This is far better then having to deal with IE6 bugs for years to come cause the vendor decided not to fix.

Anyhow, everybody who likes the IE6 approach more can go on, make an own WebKit based browser and not fix. Luckly it seems all major vendors decided against that.

Edited 2013-02-14 15:03 UTC

Reply Parent Score: 4

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

As web-developer I thank WebKit for continues fixing and improving the Web at an incredible speed. This is far better then having to deal with IE6 bugs for years to come cause the vendor decided not to fix.


How do you fix Webkit in specific browser versions?

Because the project manager really would like that all the iPad users have the same experience on his company new web site.

Or for that matter all Android users since version 2.2.

I can give more examples.

Reply Parent Score: 3