Re:Why the Nitro JavaScript Engine Isn’t Available to Other ...
by brownleej on Thursday March 17, 2011 @05:57PM
(#2338321)
Maybe the problem is that Nitro requires that an app have special permission to mark pages as executable. Apple may be comfortable giving this permission to Safari (or any if their apps, for that matter) but not comfortable giving it to third party apps. Along the same lines, it could be that apps saved to the home screen don't get Nitro because there is a special exemption low in the system for Safari, and they haven't yet worked out how to roll it out to the thin apps that are created when you save something to the home screen.
Re:Why the Nitro JavaScript Engine Isn’t Available to Other ...
by saurik on Thursday March 17, 2011 @06:02PM
(#2338340)
As someone who pulls this system apart constantly: this comment is dead on accurate.
Re:Why the Nitro JavaScript Engine Isn’t Available to Other ...
by msbarnett on Thursday March 17, 2011 @05:54PM
(#2338309)
Because if I write an app for iOS, I can't mess with Safari's address space. But if I have a UIWebView in my address space and I can use it to get a hold of memory pages with their executable bits marked, I could use that to do all manner of things that are normally forbidden.
Re:Why the Nitro JavaScript Engine Isn’t Available to Other ...
by jevinskie on Thursday March 17, 2011 @05:59PM
(#2338331)
Then why not allow at the home screen web apps to use Nitro? The entire app is within the UIWebView and controls nothing outside of it. I fail to see how a home screen web app is any different than one within MobileSafari.
Maybe they think that people are aware that the web is generally less safe and act accordingly? And they don‘t want someone to smuggle that unsafeness into apps? (The homescreen webapps are more or less just collateral damage if you take on this view.) That’s the only somewhat plausible explanation I can think of and it doesn’t make all that much sense.