4 ms·
I'm surprised that Firefox has recently slowed down on the WebAssemply implementation. Especially thinking about the tools for developers to support WASM debugg
by trzeci 5y ago
I'm surprised that Firefox has recently slowed down on the WebAssemply implementation. Especially thinking about the tools for developers to support WASM debugging with DWARF.
Unfortunately the only one solution is to use Chromium based browsers and install a plugin, that itself has some limitations (like dwarf file cannot be larger thatn 2GiB).
Sorry for a sad note in front, I'm happy because of the release!
- titzer 5y agoAlmost the entire Wasm team was acquired by Fastly.
- jd3 5y agoFor what it's worth, the Fastly team recently ported spidermonkey to WASI https://bugzilla.mozilla.org/show_bug.cgi?id=1701197 https://bugzilla.mozilla.org/show_bug.cgi?id=1701197 https://spidermonkey.dev/blog/2021/07/19/newsletter-firefox-90-91.html#-wasi-port https://spidermonkey.dev/blog/2021/07/19/newsletter-firefox-... https://bytecodealliance.org/articles/making-javascript-run-fast-on-webassembly https://bytecodealliance.org/articles/making-javascript-run-...
- titzer 5y agoYep, that's a neat development. Finally we are putting JS where it belongs, one layer above, in userspace :-)
- fulafel 5y agoThis seems like wise priorization as WebAssembly uptake is going quite leisurely and improvements in FF isn't really low hanging fruit in improving user experince.