[RodgerTheGreat]

The Birth & Death of JavaScript wasn't talking about WASM, it was talking about Asm.js, which crucially differs from WASM by being a backwards-compatible subset of JavaScript amenable to JIT compilation. The goals of these standards look similar if all you care about is transpiling c and running it on a browser, but Asm.js worked everywhere from day zero modulo performance; WASM continues to be a moving target.

[bloppe]

Wasm has long supported everything you could do with asm.js. But wasm is about much more than C to browser. That's why it's still evolving.

[leptons]

Asm.js runs on the main thread, WASM runs in its own thread.

[alex7o]

Not exactly true WASM compilcation is in a different thread, but the execution happens on the same thread as JS if you don't do any webworker stuff.

Edit: https://apryse.com/blog/how-to-enable-webassembly-threads