> [wasm] is executed in a stack-based virtual machine rather than as a native library code.<p>Wasm's binary format is indeed a stack-based virtual machine, but that is not how it is executed. Optimizing VMs convert it to SSA form, basic blocks, and finally machine code, much the same as clang or gcc compile native library code.<p>It is true that wasm has some overhead, but that is due to portability and sandboxing, not the stack-based binary format.<p>> On top of the above, memory available to WASM is limited by the browser (in case of Chrome, the limit is currently set at 4GB per tab).<p>wasm64 solves this, by allowing 64-bit pointers and a lot more than 4GB of memory.<p>The feature is already supported in Chrome and Firefox, but not everywhere else yet.