3 ms·
The parallels between WASM and the JVM are well known. But I like to think of it as WASM is building upon the knowledge gained from the JVM. With the JVM you h
by samwillis 5y ago
The parallels between WASM and the JVM are well known. But I like to think of it as WASM is building upon the knowledge gained from the JVM.
With the JVM you had to reimplement your language to target it, or design a new one. WASM was planned from the start to be a target for existing compiler frameworks such as LLVM and GCC.
With Jython you could not use extensions that were designed for CPython. With WASM you can. Take a look at Pyodide, they have ported most of the scientific Python stack to WASM, that’s not possible with Jython.
https://github.com/pyodide/pyodide https://github.com/pyodide/pyodide
- pjmlp 5y agoJust like IBM TIMI, TenDra, Amsterdam Compiler Toolkit, CLI. That is the thing with WebAssembly marketing, not being aware of bytecode formats history.
- immibis 5y agoAnd yet WASM still has warts that make it impossible to simply transpile existing binary code onto it. Java, by the way, also isn't stopping you from storing all your data in one big ByteBuffer, which is how WASM handles memory.