News for hackers. Stuff that matters.

A comment on Firefox’s new streaming and tiering compiler. Parent comment

Re:Firefox’s new streaming and tiering compiler by rmrfrmrf on Wednesday January 17, 2018 @07:47PM (#16173627)
> Why would we possibly return to a manual memory management, raw pointer oriented, assembly language level of abstraction from the much richer and safer abstraction that JS already has?

Just wait until the JVM and Flash Runtime are ported to wasm. Downloaded and compiled on every page load :).

[ Parent | on HN ]
Re:Firefox’s new streaming and tiering compiler by krapp on Wednesday January 17, 2018 @07:56PM (#16173672)
>Just wait until the JVM and Flash Runtime are ported to wasm. Downloaded and compiled on every page load :).

Why that, instead of caching common components like any other web asset, or even having the browser act as a dependency manager?

There are bound to better solutions than "download and compile on every page load."

[ Parent | on HN ]
Re:Firefox’s new streaming and tiering compiler by adrianN on Thursday January 18, 2018 @01:20AM (#16175116)
Users could for example install plugins into their browser.
[ Parent | on HN ]
Re:Firefox’s new streaming and tiering compiler by pjmlp on Thursday January 18, 2018 @01:25AM (#16175140)
Slow and steady. :)

http://www.teavm.org/

https://github.com/JasonHuang3D/AJC-Flash-WebAssembly-Exampl...

http://www.mono-project.com/news/2018/01/16/mono-static-weba...

[ Parent | on HN ]