4 ms·

This doesn't even really apply to wasm though. That is the big difference. You would have a runtime that can execute wasm, and its all the same. Any browser can

This doesn't even really apply to wasm though. That is the big difference. You would have a runtime that can execute wasm, and its all the same. Any browser can run wasm provided you don't try unsupported sys-calls.

throwway120385 3y ago
The point I'm trying to make is that what is being described as a "revolutionary" approach -- that of putting all of your application code into a single binary -- is just static linking but using wasm plus a small JavaScript engine. It's revolutionary if your whole experience is with Node.JS inside of Docker, but from my perspective it's the rediscovery of a 50 year old technology. Just with TypeScript/JavaScript in a browser engine. To be clear this is a great idea and will solve a lot of problems, but it's not like people haven't thought of this before today.