[muvlon]

With this technology's death, the thread of prophecy is severed. Restore a saved game to restore the weave of fate, or persist in the doomed world you have created.

[tadfisher]

Yagrum Bagarn has something for you.

[mikece]

Not really: ASM.js became WASM. What killed the possibility of WASM being The One Way to run everything is AI... the one wildcard that Gard Bernhardt didn't predict.

[DarkUranium]

To be honest, with how bad a target WASM is for any existing compiler, I feel like what killed that possibility was WASM itself.

Its IR design is horrendeous.

[nextaccountic]

Can you talk more? I've seen people say only good things about wasm

[avadodin]

Not op, but I only know it as the 32-bit single-threaded binary replacement for JavaScript that can't interact with anything naturally yet people get all excited about when they manage to turn their LLVM slop output into it.

Maybe we've been reading different HN submissions.

[nextaccountic]

That was only the MVP.

Wasm nowadays is 64 bits (except for Safari, the IE6 of our time) and has threads.

True about the wasm inability to call JS APIs with no overhead. This sucks