4 ms·
If you were around ~25 years ago, you likely remember the idea that JVM will run everywhere and replace everything. (And some XML on top.) Indeed, JVM can run
by nine_k 3y ago
If you were around ~25 years ago, you likely remember the idea that JVM will run everywhere and replace everything. (And some XML on top.)
Indeed, JVM can run everywhere, and has reached far and wide, from SIM cards to huge servers. But it has not replaced all other runtimes, even when it achieved really good GC and and near-native speed thanks to JIT compilation.
WASM is very similar to JVM in many regards. It will reach far and wide, it will supplant a few things, but I bet it's not going to replace too many things, let alone native code in containers.
- jw1224 3y agoWASM is a compiler target for countless languages, unlike JVM which is tied to Java. That’s what makes it incomparable to JVM… It’s a global runtime-on-demand for whatever you throw at it.
- hajile 3y agoSecurity and universality are the biggest differences here. WASM was ground-up designed with security in mind (learning from earlier projects like pNaCl). Likewise, WASM was designed with a lot of language targets in mind rather than just Java.
- pjmlp 3y agoSure, if we ignore internal memory corruption inside linear memory. JVM might not be the ideal example of polyglot runtime, yet there are several others of the same vintage, designed with multiple languages in mind, including C and C++, e.g. CLR, TIMI,...