3 ms·
On iOS it won't be that quick: you don't get anything more than the JS interpreter, as you cannot allocate any executable memory on iOS, so any JITing compiler
by gsnedders 13y ago
On iOS it won't be that quick: you don't get anything more than the JS interpreter, as you cannot allocate any executable memory on iOS, so any JITing compiler is out of the question.
- udp 13y agoWouldn't this be exempt from that limitation, with the JavaScript engine being distributed as part of iOS itself?
- gsnedders 13y agoNo, it applies per process: whether or not it came from a dynamically linked library distributed as part of the system is irrelevant. This is why UIWebView is slower outside of Safari.
- pi18n 13y agoThey might be moving towards some kind of XPC service so you can talk to a JIT through a Mach port. Speculation is my own, derived from: http://oleb.net/blog/2012/10/remote-view-controllers-in-ios-6/ http://oleb.net/blog/2012/10/remote-view-controllers-in-ios-...