3 ms·
You might be confusing Android with WP8. Both iOS and WP8 do that. Android doesn't. You can embed V8 in your app in Android. The security reason is mainly BS t
by mtgx 14y ago
You might be confusing Android with WP8. Both iOS and WP8 do that. Android doesn't. You can embed V8 in your app in Android.
The security reason is mainly BS to keep off competing browsers from the platform.
- pifflesnort 14y ago> The security reason is mainly BS to keep off competing browsers from the platform. Actually, it's mainly BS to ensure control over code signing and distribution. W|X pages would mean that you could download and run arbitrary native code, and Apple can't have that. It does also provide some nominal security advantage, but I think that's a pretty ridiculous trade-off overall.
- juiceandjuice 14y agoI'd argue it's to keep developers locked in to Objective-C and iOS. Facebook tried going the HTML5 route in the native iOS app, but everything was too slow (it was comical how much faster facebook.com was in Safari vs running the app) until they ultimately switched back to Objective-C.
- cpeterso 14y agoIt's ironic that Objective-C was an albatross on the neck of Mac OS X, a platform with small marketshare and an uncommon application framework. Now, Objective-C is a key advantage for Apple's vendor lock-in keeping iOS developers from (easily) porting to Android.
- vvhn 14y agoFacebook's HTML 5 Android App really showed everybody how they were being constrained by iOS' restrictions...
- st3fan 14y agoI am probably the only person here but I do not think it has much to do with keeping alternative browsers off the platform or preventing people from using UIWebViews. They already have a clause for third party browsers in the submission/review guidelines so there is no need for the existence of a technical reason to enforce that. I truly think the real reason is security. The problem with allowing rwx pages in an iOS process via WebKit is that they can be used by the native app to load rogue code in. This is a really difficult problem to solve and I honestly think Apple chose the easy way out: disallow it all. I do think a solution is coming though. Already in iOS6 a bunch of ViewControllers are running out of process. See the link below. I think this will lead to out of process, and fully JITted WebKit in a future release. Many times people think Apple is making some weird technical decision on purpose to annoy developers it is really just a pragmatic decision to get a product out of the door on time. This happens all the time and everywhere. At Google, Mozilla, Apple, Blackberry and Canonical. http://oleb.net/blog/2012/10/remote-view-controllers-in-ios-6/ http://oleb.net/blog/2012/10/remote-view-controllers-in-ios-...