Linked by Thom Holwerda on Wed 13th Feb 2013 13:21 UTC
Permalink for comment 552490
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2006-01-25
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?