Re:Apple starts rejecting apps with “hot code push” features
by kalleboo on Wednesday March 08, 2017 @05:01AM
(#13819209)
The rules explicitly forbid any HTML renderer or JS interpreter aside from WebKit, JIT or no JIT. I believe all the popular third party browsers today still use the non-JIT UIWebView rather than WKWebView because the former gives you more control over the request cycle
[ Parent
| on HN ]
Re:Apple starts rejecting apps with “hot code push” features
by Operyl on Wednesday March 08, 2017 @07:32AM
(#13819779)
Except, apparently, Chrome
https://blog.chromium.org/2016/01/a-faster-more-stable-chrom...
Re:Apple starts rejecting apps with “hot code push” features
by Xylakant on Wednesday March 08, 2017 @08:53AM
(#13820209)
Chrome uses WKWebView on iOS, so it's basically safari with a different UI (so does firefox on iOS)
Re:Apple starts rejecting apps with “hot code push” features
by Operyl on Wednesday March 08, 2017 @11:03AM
(#13821116)
Yes, I know. I was saying the OP of this thread was wrong because it's not UIWebView, it's WKWebView with a JIT :).
Re:Apple starts rejecting apps with “hot code push” features
by je42 on Wednesday March 08, 2017 @02:19PM
(#13822814)
WKWebView has JIT. In executes the JS in a different process than the hosted app; there the JIT lives, this special process is whitelisted to do JIT magic.