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 552311
To read all comments associated with this story, please click here.
Sad, but understandable
by aargh on Wed 13th Feb 2013 13:32 UTC
Member since:

Sad, but understandable. Well explained, Thom. I added a +1 for the article.

Reply Score: 9

RE: Sad, but understandable
by bassbeast on Wed 13th Feb 2013 21:35 in reply to "Sad, but understandable"
bassbeast Member since:

No it is NOT "understandable" it is monopolistic practices that need to be busted. we ALL know what this is about, Cupertino using undue influence on the market, from trying to control the price of books to deciding what video format an "open" web is supposed to run on (which won't be open much longer if Apple has their way, H.264 is controlled by one of the worst patent trolls out there and ask Mozilla how friendly they are to FOSS) its all about Apple being the 800 pound gorilla and making the world bend to them thanks to their locked down platform.

does anybody here HONESTLY think Opera would be abandoning presto if it would run on iPhone? I was against MSFT when they used IE to try to gain more control, I am against Apple using iPhone/iPad to gain more control. No matter which OS or device you use the web should be about openness and choices NOT about a single corp dictating everything, and especially not a single corp that is sue happy and a control freak dictating control. we should ALL be royally po'd at this, we are losing choices left and right and its all due to Cupertino and how much influence they are having on the markets.

Reply Parent Score: 1

RE[2]: Sad, but understandable
by PresentIt on Wed 13th Feb 2013 21:49 in reply to "RE: Sad, but understandable"
PresentIt Member since:

does anybody here HONESTLY think Opera would be abandoning presto if it would run on iPhone?

Of course they would. If it was just about iOS they could use Webkit there and Presto everywhere else. But this is a switch across the board.

Reply Parent Score: 5

RE[2]: Sad, but understandable
by galvanash on Thu 14th Feb 2013 20:30 in reply to "RE: Sad, but understandable"
galvanash Member since:

does anybody here HONESTLY think Opera would be abandoning presto if it would run on iPhone?

I don't follow... It isn't about presto not running on iPhone. Their new webkit based browsers won't run on iPhone either...

Apple doesn't have a policy disallowing browser engines other than webkit - their policy is they do not allow any browser engines. You either use the native UIWebView class (i.e. Safari) or you don't use a browser engine at all and send everything to external servers for rendering (i.e. Opera Mini). In either case, your browser is NOT using webkit directly - using UIWebView is completely different from using webkit.

Chrome, for example, is a webkit based browser... But the iOS version does not include webkit at all - it just wraps around UIWebView. How is being webkit based an advantage for iOS deployment when you in fact cannot use it?

Personally, while I share a lot of the sentiment about Opera dropping Presto - it really only boils down to one thing: Opera would rather concentrate on making browsers than making browser engines. Presto, while it is overall an excellent engine, is not gaining traction - it never really has, and it offers no competitive advantage anymore. There is certainly an argument that its existence helps with maintaining web standards (which is why I am sad to see it go), but from a business point of view, why bother?

Reply Parent Score: 4