It's similar in that it adds even more overhead to just running your software to make your life just a tiny bit easier. You don't need to think about files and networking if you can't do any IO, after all!
I don't see how webassembly would by any different from just running a JAR file or similar in terms of ease and usability. It's just a new method of writing bytecode that can do less. Bytecode interpreters already struggle to make efficient use of things like SIMD and this is just another layer on top of that.
What's the point of using low level languages if you're going to compile them to semi bytecode. You can already set up virtual machines with predetermined state of any kind, see Firecracker for example, there's no need for a WASM overlay.
WASM is a cool technology, don't get me wrong, but in my opinion this is a stupid way to use it.
I don't see how webassembly would by any different from just running a JAR file or similar in terms of ease and usability. It's just a new method of writing bytecode that can do less. Bytecode interpreters already struggle to make efficient use of things like SIMD and this is just another layer on top of that.
What's the point of using low level languages if you're going to compile them to semi bytecode. You can already set up virtual machines with predetermined state of any kind, see Firecracker for example, there's no need for a WASM overlay.
WASM is a cool technology, don't get me wrong, but in my opinion this is a stupid way to use it.