4 ms·
It would be lovely if the whole firefox's html/css/js engine was compilable into webassembly. A new browser could implement webassembly compiler and use firefox
by gix12 6y ago
It would be lovely if the whole firefox's html/css/js engine was compilable into webassembly.
A new browser could implement webassembly compiler and use firefox rendering engine as a fallback for when their novel rendering engine doesn't support some feature on a website.
Taking it further - the website author could possibly specify rendering engine it prefers to be rendered with(as specific version could simply be downloaded on demand from cdn, like common js/css libraries are).
And pure webassembly apps (ie flutter) could skip the html/css/js bloat altogether.
- rini17 6y agoThis won't do, from the myriad issues I'll pick one: you might encounter an unsupported feature seconds into page loading, or even later, after user already entered some data.
- gix12 6y agoThat is if you allow dynamic code loading or such dom manipulation to allow it. But for such cases, you should have already started the fallback engine the first time you scanned through the website code. But fair enough. In the wild you would have to use fallback pretty much always. Still, webassembly-able gecko would be handy and would allow for experimenting with above mentioned streamlined 'web standard'. Web author could simply sign it's compliance to the 'standard' using meta tags, http headers or some other way.
- R0b0t1 6y agoI find it hilarious that you've basically arrived at what Java tried to do so many years ago.