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 552408
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Comment by ssokolow
by Tony Swash on Thu 14th Feb 2013 01:00 UTC in reply to "RE[3]: Comment by ssokolow"
Tony Swash
Member since:
2009-08-22


Yeah well that what happened to the other companies with IE6 back in 2001 ... and that turned out soooo well didn't it?

We had no browser innovation for years. Everything was written for the one browser.

The same is happening with webkit but in the mobile space.
other too.


I think the difference is in intent, which in turn is a function of business model. Right from the start Microsoft saw the web as a threat to it's business which was to ensure that everything that supported it's OS/Productivity monopoly flourished and everything that even remotely threatened it or even opened an alternative space did not flourish. Microsoft thought that a neutral browser that ran equally well on any platform undermined it's platform strategy. It's answer was a closed proprietary browser engine and the crushing of netscape by leveraging the Windows OS monopoly. Once netscape was finished and IE ruled Microsoft lost interest in browser development because they didn't want the web to be a rich and developing experience, they wanted it to be a tepid backwater compared to Windows apps.

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.

Reply Parent Score: 5

RE[5]: Comment by ssokolow
by moondevil on Thu 14th Feb 2013 06:23 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[5]: Comment by ssokolow
by lucas_maximus on Thu 14th Feb 2013 08:26 in reply to "RE[4]: Comment by ssokolow"
lucas_maximus Member since:
2009-08-18

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


You miss the point, everything will be built for Webkit first and everything else second, just like it was for IE6 ... because developers aren't following the spec they are developing for Webkit only.

Reply Parent Score: 4

RE[6]: Comment by ssokolow
by cyrilleberger on Thu 14th Feb 2013 09:02 in reply to "RE[5]: Comment by ssokolow"
cyrilleberger Member since:
2006-02-01

You miss the point, everything will be built for Webkit first and everything else second, just like it was for IE6 ...


And that is a problem ? IE6 was a problem for two reasons:

1) it was not developed anymore, meaning no progress
2) only available on a single platform

IE6 was all about locked-in, locking users on windows, and locking users on microsoft technologies. All of that is not possible with Webkit. Since it is LGPL, it cannot become proprietary, and, if Apple cannot prevent others to use Webkit on different platform, also Apple cannot stop progress, if Apple decides to stop development of Webkit, no problem, Google and Opera will carry on the work, and it will give them a competitive advantage over Apple. This is the major difference between IE6 and Webkit, one was blocking progress, the other one cannot.

because developers aren't following the spec they are developing for Webkit only.


Shame on developers for developing website that works in real life instead of developing website that would work in a theoretical world...

That said, there is still the need for a good specification to make sure that rendering does not get broken across version of webkit. And that is an area where Opera is a very welcomed addition to the webkit world, they have always been the best at respecting the specification.

Reply Parent Score: 5