News for hackers. Stuff that matters.
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
Re:Apple starts rejecting apps with “hot code push” features by Operyl on Wednesday March 08, 2017 @07:32AM (#13819779)
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.
Re:Apple starts rejecting apps with “hot code push” features by Operyl on Thursday March 09, 2017 @02:38PM (#13832564)
I understand that, the original OP was stating that none of the "browser skins" had JIT because they all used UIWebView, which isn't the case with the link I posted :p.