3 ms·
> But I thought WASM was to replace .NET and JAVA VM's. It's name is literally web assembly. It's goal was never and still isn't to replace those VMs. It was l
by troupo 3y ago
> But I thought WASM was to replace .NET and JAVA VM's.
It's name is literally web assembly. It's goal was never and still isn't to replace those VMs. It was literally an idea to create a faster code sandbox for the web based on the idea's from Mozilla's asm.js
> to be more a pass through to the underlying CPU. So much faster. So compile down to a 'byte code' like thing, that does not run on a VM, but runs on the underlying HW.
wat.
> So goal was speed. And to allow other languages to compile to it.
Yes, it was. Has nothing to do with the fantasy of replacing JVM and .Net VM or running directly on hardware.
- FrustratedMonky 3y agoOf course, that is where it started. I'm probably being loose in terminology. I assumed that to gain this speed, that it was a little closer to the metal than a VM like Java. That it must have some kind of pass through to allow commands to run on the local HW, not just emulated in a VM. So like a VM in that you can compile to it, but it would execute natively. From the FAQ. "WebAssembly aims to execute at native speed by taking advantage of common hardware capabilities available on a wide range of platforms. It is a low-level assembly-like language with a compact binary format that runs with near-native performance" And when looking at the Use Cases, it seems to be trying to do a lot more than javascript. https://webassembly.org/docs/use-cases/ https://webassembly.org/docs/use-cases/