Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Do you know of these security privileges? I've never heard either google or mozilla complain about them.


A browser's JIT needs permission to dynamically generate code and then execute it, which is the primary permission Apple doesn't grant to third parties.

Other browsers on iOS just wrap Safari's WebKit in a different UI.


They're not allowed to ship their own engines, in addition, rather than this being framed as a JIT issue.


This isn't true, other browsers can run JITless. JIT is a performance optimization to be sure, but this doesn't explain why Apple bans other browsers. See https://twitter.com/slightlylate/status/1274012259451207681

Disclosure: I work at Google, formerly Chrome team, never worked on this.


I didn't know about this. Thanks for sharing. It does mention a 40% performance impact to running JITless. What is the power impact?


V8 has a pure interpreted mode for JavaScript and RegExps: https://v8.dev/blog/jitless

Many sites only need light JavaScript usage and would not run significantly slower. wasm is not supported in jitless mode. Link pulled from twitter link in sister comment by rictic.


It destroys battery life though.


Code generation is not a safety issue. If you have the privileges to run code then generating code should not cause more problems unless the OS has significant vulnerabilities.


I think they had fixed this in the latest iOS versions. It is good for AAA game engines and such as well.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: