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 552349
To view parent comment, click here.
To read all comments associated with this story, please click here.
Fergy
Member since:
2006-04-10

Oh, At first I thought you were saying that the other browsers also abandoned their engines to focus on ui. But I understand you're saying that Opera will now just be like them, only doing ui.

Fair enough, however Opera has actually invented most of the modern web browser ui that I find useful (tabs, quick dial, etc). Its the engine that it usually fell short on. So I look forward to it being able to innovate without having to constantly fix their javascript support.

Yeah sorry I could have been more clear. But I don't care about who was first. I care about who does it best. Opera is number 2 for me(Firefox is 1). Opera feels fast and reliable. The speed of Chrome with the nice Opera GUI would be an improvement on Chrome but a step backwards for Opera.

Edited 2013-02-13 18:10 UTC

Reply Parent Score: 2

telns Member since:
2009-06-18

I've been using Opera almost exclusively since somewhere around the 5.x or 6.x days.

Releases 10+ took a big nosedive in reliability. Even so, I'm pretty saddened by this news. I'll still stick with the Presto versions as long as I can.

Reply Parent Score: 1

telns Member since:
2009-06-18

The are two things about Presto; one is that it tends to be standards compliant almost to a fault. If you make a site look good in Opera, you are almost guaranteed it is going to look fine in all the other browsers.

But even for everyday users rather than developers, when a company has developed a UI and engine side by side for years, a lot of the UI features come to depend on engine features. They work together.

Dragonfly is the most obvious example, but there will be tons of other things, affecting addons, and custom CSS filters, and the like. There is no chance that WebKit offers exactly the same hooks into that Presto does.

Most of the 'big' features they will adapt, I am sure, but all along the margins you can expect them to lop off the stuff that is really hard to do (cause for whatever reason, the object you need that is readily accessible in Presto is buried ten layers deep in WebKit) or not a big enough feature to be worth the effort--except it was the feature you used everyday.

In short, it is almost certain that some of the features that exist now won't exist in the initial WebKit releases, and may never come back.

Reply Parent Score: 5

PresentIt Member since:
2010-02-10

I remember when people were talking about how version 8+ took a big nosedive in reliability. And before that, version 6+. And basically every major version.

Apparently Opera has been taking big nosedives from the very start, if one is to listen to people like you.

Why stick with Presto btw?

Reply Parent Score: 3