WebAssembly vs JVM
Discussions compare WebAssembly to JVM bytecode, native binaries, JavaScript, and other VMs, questioning its advantages, uniqueness, and necessity as a compilation target.
Activity Over Time
Top Contributors
Keywords
Sample Comments
I honestly don't really get how wasm solves this issue. How is it better for this than natively compiled binaries or java bytecode?
And wasm is a compilation target for languages that aren’t JS, a pretty big advantage in my book
Can someone explain to me what makes Wasm any better and/or different than Javascript bytecode.
Don't see the point in this unless someone were to write a HotSpot backend that generated WASM.
Genuine question: outside of the web browser, what's the advantages of WebAssembly over the JVM or a similar VM?
But WASM already exists and has many languages that are able to compile to it, why reinvent the wheel?
What would "support other languages natively" give you that WebAssembly doesn't?
I'm curious, why not use JVM bytecodes for web assembly... or actually any of the legitimate, mature, optimized, hardened runtimes out there? I feel like we're reinventing the wheel, again.
There is none, one of the main objectives of WASM was to be a machine agnostic bytecode, similar to JVM bytecode for example. People have even built wasm VMs on FPGAs
No. Wasm is not useful enough yet. Neither are containers.