3 ms·
They are forced to use JavaScriptCore, in the sense that you can't execute JIT-compiled code except for within that one blessed, sandboxed framework. I don't b
by dwaite 7y ago
They are forced to use JavaScriptCore, in the sense that you can't execute JIT-compiled code except for within that one blessed, sandboxed framework.
I don't believe they have ever been limited in porting, but have decided the performance hit for using their own javascript engines (or compatibility issues in leveraging Apple's) aren't worth the effort.
- jakub_g 7y agoEven more, the WebView on iOS is not Safari. It's dumbed-down Safari that does not support certain features that Safari supports (service workers and all PWA-related stuff). So it's not equal competition at all.
- chrisseaton 7y agoI'm pretty sure it's exactly the same code base just with some minor feature flags.
- NicoJuicy 7y agoNot that minor, there are indeed 2 different engines. One for Safari and one for the rest.
- saagarjha 7y agoRight, but that comes out of the exact same code with some minor feature flags.
- zapzupnz 7y agoYou're parroting old news. The different engine is for UIWebView which is now deprecated in favour of WKWebView which uses Safari's Nitro engine. Websites saved to the home screen use UIWebView's engine — but that's not the discussion, the discussion is about browser apps which can and do use WKWebView.
- st3fan 7y agoBesides technical limitations: the iOS App Store rules are clear: it is simply not permitted.