Why has Apple limited the Nitro JavaScript engine in iOS 4.3 to Safari?
Well, it’s tricky, because they did Nitro in the first place to speed up web page. I have heard it was a bug in the way the JIT worked because it allows to run native code. Now, that would make sense for the UIWebView, since they do not want to give a way to call native API from JS. However, for full-screen mobile safari application, I do not make the connection (if it is safe to run it on Mobile Safari, why full-screen would change anything?). Now, I think it has to be a technical issue and not a business one (as we might want to think). It would take great malice to turn Nitro off for HTML5 Apps just for business reasons (to keep people in the Native SDK). I do not see middle management or engineers playing this game and it would be borderline dishonest for an exec to send this request down. Here is a good article about it: http://www.theregister.co.uk/201…
