> This is why having a compilation target that works the same way everywhere would be so valuable. We're some ways away from this, but I think WebAssembly offers hope here.
Why does WebAssembly offer more hope than the JVM, or interpreted languages that we already have? It will still have to interop with native libraries to get work done.
It's lower level than the JVM and more of an abstraction over hardware. So native libraries can be compiled directly into it, so everything can interop on top of Wasm.
The jvm is explicitly designed to run the Java language. It has Java's type system baked into the bytecode. It is not an abstraction over hardware. (it doesn't even have unsigned comparisons :()
Why does WebAssembly offer more hope than the JVM, or interpreted languages that we already have? It will still have to interop with native libraries to get work done.