asm.js was a thing before WebAssembly, with the same downsides, except maybe a little less browser support for debugging, inspecting, etc. asm.js was able to exist without browser support in Chrome, so WebAssembly support doesn't really bring anything new to the table.
At least that's how I understand it, care to give ideas why it's not a positive change? :)
> care to give ideas why it's not a positive change?
What I wrote above: it's going to encourages 10x more bloated and obfuscated websites.
Apart from the security and privacy issues, it will make the web even less accessible to users with slower Internet connections (some 2bln people) and visually-impaired users.
WASM is fast enough that you can internally sell it as "speed improvement" to keep your developers happy and who else might question your intentions.
asm.JS tends to be slower than direct JS.
