I think you're missing the core use-case of WASM. It's not for general app development, which will stay with JS. It's meant to provide plug-able, high-performa

I think you're missing the core use-case of WASM. It's not for general app development, which will stay with JS. It's meant to provide plug-able, high-performance functions for heavy computational tasks - crypto, game rendering, heavy in-browser data analysis, etc etc. I double JVM in WASM makes sense at all - though somebody will probably do it in anyway. WASM is not meant to be good at Garbage Collection, etc. It's not a design goal at all.