Firefox’s Fight for the Future of the Web

Re:Firefox’s Fight for the Future of the Web by radarsat1 on Sunday November 17, 2019 @06:56AM (#21557560)

Ah, so it is all about the javascript engine? Ok I can see how that might put up some major technical barriers, but still it should be technically feasible to have the firefox rendering engine make use of the iOS javascript engine, no? Maybe it's not worth the effort of course. I am just trying to get a feel for what the barriers are.

[ Parent | on HN ]

Re:Firefox’s Fight for the Future of the Web by sharpneli on Sunday November 17, 2019 @07:20AM (#21557622)

Not via public apis. So cannot be placed into app store.

[ Parent | on HN ]

Re:Firefox’s Fight for the Future of the Web by KonkeyDong69 on Sunday November 17, 2019 @07:34AM (#21557668)

In addition to what the other replies said, feel free to eyeball the code required to embed SpiderMonkey in Firefox at https://github.com/mozilla/gecko-dev/tree/master/dom/binding.... It's rather large and complex.

[ Parent | on HN ]

Re:Firefox’s Fight for the Future of the Web by padenot on Sunday November 17, 2019 @09:48AM (#21558090)

This is not at all the code to embed SpiderMonkey in Firefox, those are the bindings from DOM APIs to the implementation of those APIs in Firefox. Above that, calling into this layer, is another layer that transforms JS calls into C++ calls (roughly).

The interface between SpiderMonkey and the rest of Firefox is here: https://searchfox.org/mozilla-central/source/js/src/jsapi.h.

[ Parent | on HN ]

Re:Firefox’s Fight for the Future of the Web by vbezhenar on Sunday November 17, 2019 @07:22AM (#21557626)

I think that iOS JS engine is tied to WebView and it would be hard to re-use it with other rendering engine.

[ Parent | on HN ]

Re:Firefox’s Fight for the Future of the Web by saagarjha on Sunday November 17, 2019 @08:18AM (#21557802)

JavaScriptCore can be used can be used independently from the rest of WebKit, but I’d expect it to be slow.

[ Parent | on HN ]