5 ms·

And it doesn't run the JIT compiler. Which means all 3rd party browsers in non-jailbroken iOS are slower than Safari and Phonegap apps are a lot slower than nat

And it doesn't run the JIT compiler. Which means all 3rd party browsers in non-jailbroken iOS are slower than Safari and Phonegap apps are a lot slower than native apps.

sspiff 13y ago
I had heard about the JS runtime restriction (which is why I was interested if Opera had avoided it somehow), but never heard about the JIT restriction. Is the JIT disabled for all third party apps? I was going to make a joke about Soviet app stores, but realized this isn't the place.
- rahoulb 13y ago
  The JIT restriction is because the OS won't let you mark data pages as executable for security reasons (Safari, as a trusted app, is the only exception). EDIT: changed wording for clarity
  - sspiff 13y ago
    Thanks for clarifying. I learned something new today.
captn3m0 13y ago
Just noting that a "Nitrous", available on Cydia for jailbroken iPads, enables Nitro (JIT compiler for Safari) on all browsers.
bla2 13y ago
It means javascript execution is slower in 3rd-party browsers. They can make up for that by e.g. using better networking libraries: http://www.guypo.com/mobile/ios-browsers-speed-bakeoff/ http://www.guypo.com/mobile/ios-browsers-speed-bakeoff/
- sspiff 13y ago
  That still means it's a very asymmetric competition: by default, Apple has a significant head start because of the JIT. If others have to do some crazy engineering on networking libraries, nothing stops Apple from reusing the concepts the competition implements. The competition does not have this possibility with javascript engine improvements.
  - bla2 13y ago
    No argument here. Just saying that performance is about more than js performance.