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 552490
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Sad, but understandable
by galvanash on Thu 14th Feb 2013 20:30 UTC in reply to "RE: Sad, but understandable"
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