they're indeed very similar
the main difference distills down to execution/implementation
java applets were slow, wasm is fast
that distinction makes a categorical difference
the main difference distills down to execution/implementation
java applets were slow, wasm is fast
that distinction makes a categorical difference
I guess I'm wondering what makes WASM so much better than investing engineering energies into existing things.
if you're deploying wasm to the browser, then native means your JS engine
if you're deploying wasm to the server, then native means actual machine code
the competitive advantage versus java is (at a very high level) the language design -- java is much higher-level than wasm, which limits its potential