Looking forward to progress on the memory control proposal(s).
Another reason to want more than 4GB of memory is to have more address space, assuming that you have the ability to map it. With that capability Wasm64 could be useful also for apps that don't plan to use a huge amount for real.
ARM already have a special instruction `FJCVTZS` to accelerate JavaScript. If WebAssembly gets popular enough there will probably be hardware acceleration for it.<p><a href="https://community.arm.com/arm-community-blogs/b/architectures-and-processors-blog/posts/armv8-a-architecture-2016-additions" rel="nofollow">https://community.arm.com/arm-community-blogs/b/architecture...</a><p><a href="https://stackoverflow.com/questions/50966676/why-do-arm-chips-have-an-instruction-with-javascript-in-the-name-fjcvtzs" rel="nofollow">https://stackoverflow.com/questions/50966676/why-do-arm-chip...</a>
The reason I don't use WebAssembly is that browsers do not support the text format.<p>Often it is just a tiny loop that one wants to optimize. Writing it manually in WAT would be nice. But adding a whole toolchain and a compile step to the stack is not worth it.<p>Shouldn't it be straight forward to compile WAT to WASM? I hope one day browsers will support it.
Unless you want to install a crypto miner to run locally on someone's machine when they visit a website.<p>Now possible with this as well as even more capable closed-source untrusted binary blobs with DRM running amock on your machine.<p>Mozilla (a member part of the W3C) and was supposed to stop such DRM-like software from reaching the web. They have proven to be powerless to allow such software like this to be approved as a web standard.<p>The ones cheering WASM are the ones who absolutely love DRM and malware blobs in your machine now accessible in the browser.<p>This is a massive failure of the so-called "Open Web".
"How do browsers take advantage of this fact? By reserving 4GB of memory for every single WebAssembly module."<p>Does reserve mean it has exclusive access to? Because it can't possibly be that every single wasm module takes 4GB!
TL;DR: no, unless you actually need more than 32-bit address range. The other advantages of 64-bit CPUs (e.g. 64-bit integer registers, more general purpose registers) are already taken advantage of by wasm32.