News for hackers. Stuff that matters.
Re:Firefox’s Fight for the Future of the Web by fauigerzigerk on Sunday November 17, 2019 @09:55AM (#21558129)
But why is JavaScript JIT compilation tied to the rendering engine?
Re:Firefox’s Fight for the Future of the Web by andrewl-hn on Sunday November 17, 2019 @10:28AM (#21558318)
Yep. technically, Apple doesn't force Firefox to use WebKit. They could still use their Gecko WebRenderer and use Apple's JavaScriptCore to run page scripts. Same goes to Chrome: Blink + JSC instead of Blink + V8.

In practice in seems like both Chrome and Firefox have their renderers and JavaScript runtimes so tightly integrated that it's very hard to replace the later.

Re:Firefox’s Fight for the Future of the Web by fauigerzigerk on Sunday November 17, 2019 @10:47AM (#21558397)
Elsewhere in this debate sharpneli says that there is no public API to call into JavaScriptCore and using non-public APIs violates the App Store rules. So that would explain it.
Re:Firefox’s Fight for the Future of the Web by saagarjha on Sunday November 17, 2019 @03:14PM (#21559812)
There is API to use JavaScriptCore in your apps: https://developer.apple.com/documentation/javascriptcore. No JIT, though, so it’s slow.