You might already know this, but WASM isn't even at a stage where it can replace JS. Bindings to the browser APIs are currently done through a JS bridge, which

You might already know this, but WASM isn't even at a stage where it can replace JS. Bindings to the browser APIs are currently done through a JS bridge, which can be pretty slow. I've lost track of the process (there were several proposals) so I'm not sure where we're at now. I guess not much changed, so the current state of WASM is mostly for porting and running non-JS code (such as Go's here) in the browser. It's also faster than JS (if passed through an optimizing compiler) so it might be useful for non-IO-bound code. Outside the browser it's being used as a sort of universal bytecode (a la JVM). https://wasmer.io/ https://wasmer.io/