3 ms·
I agree, that would suck. Specially if -for some reason- we start seeing differences in terms of rendering speed/js engine/or other techs between the android ve
by beshrkayali 14y ago
I agree, that would suck. Specially if -for some reason- we start seeing differences in terms of rendering speed/js engine/or other techs between the android version and the iOS version.
- vladikoff 14y agoThis is already true today.
- beshrkayali 14y agoWell, then it's already sucky :) I never tried/used the android version.
- aniket_ray 14y agoThe Android and iOS versions have always been different. Apple does not approve any browser apps that do not use the default UIWebView. It was this reason that Adobe could never launch a flash enabled browser on iOS.
- ionforce 14y agoThere already are speed differences in iOS alone. The native Safari has a faster JavaScript engine than the sandboxed Safari instances that iOS apps use. Or something like that. Something about security concerns.
- svachalek 14y agoIt's the JIT for JavaScript that's disabled. I've never seen an official statement on it but I've read that it's that the security model in iOS does not allow compiling code and then executing it, but Mobile Safari gets a unique bypass for this security. Other apps which merely embed a UIWebView are stuck with interpreted JavaScript.
- basch 14y agounless you have nitrous installed. http://lifehacker.com/5930405/nitrous-speeds-up-google-chrome-for-iphone-with-the-nitro-javascript-engine http://lifehacker.com/5930405/nitrous-speeds-up-google-chrom...
- gsnedders 14y agoAny user process cannot allocate executable memory, hence you cannot have any JIT.