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 552386
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Sad....
by PresentIt on Wed 13th Feb 2013 21:28 UTC in reply to "Sad...."
Member since:

The sad part about it is 'if everything is the same under the hood', browsers will just compete for user's attention and with each other on UI features and such?

Yes, so? That means the part you actually notice will be different.

So why use Opera at all then, use the WebKit browsers already existing, if Opera introduces a killer feature, just wait a bit, and your favorite WebKit browser will have it soon (that is the way of it usually right?).

What prevents those Webkit browsers from doing the same when Opera is using Presto?

How does switching to Webkit make any difference when it comes to the UI?

I don't see how Opera will be more valuable in any industry that is already controlled by 'established' WebKit browsers.

How is it more valuable today? Because it has an engine with lots of compatibility problems?

Maybe continued and maybe better innovation 'under the hood' would have been a better game changer?

They tried that. But when they added some new standard, the other browser ignored it and added their own instead, forcing Opera to implement that instead.

Reply Parent Score: 3