[_jn]

Can't help being reminded of that talk by Gary Bernhardt: “The Birth & Death of JavaScript”[0] — exploring a hypothetical future where JS takes over everything without (most) anyone using it of their own volition.

0: https://www.destroyallsoftware.com/talks/the-birth-and-death...

[tokyodude]

Except entirely irrelevant as WASM is not Javascript.

[techntoke]

Can you show me an example of a WebAssembly app that runs in the browser with JavaScript enabled?

[grungleshnorts]

There are probably newer examples, but from when WebAssembly was coming out:

https://s3.amazonaws.com/mozilla-games/ZenGarden/EpicZenGard... (from https://www.webassemblygames.com/ )

https://alpha.iodide.io/

https://www.figma.com/blog/webassembly-cut-figmas-load-time-...

https://github.com/mdn/webassembly-examples/

https://github.com/emscripten-core/emscripten/wiki/Porting-E...

[techntoke]

Meant to say with JavaScript disabled.

[_jn]

Sure, though it’s still a web technology taking over an otherwise unrelated space ¯\_(ツ)_/¯

[int_19h]

I don't think it's unrelated. Despite the name, WASM isn't really a "web technology" - it's a sandbox technology and a compile-once-run-everywhere technology, and there has always been demand for that outside the web, even before the web existed. It might be that the web is what created enough demand for it to happen in the end, but what do we care?

The problem with JS was never that it's a web technology. It's that it's a bad technology that happened to be in the wrong place at the wrong time to get a first mover advantage.