WebAssembly (abbreviated Wasm) is a binary instruction format for a stack-based virtual machine. Wasm is designed as a portable compilation target for programming languages, enabling deployment on the web for client and server applications.
These all sound like good improvements to WASM as a binary target, but… how do we STILL not have access to any kind of I/O? How is that not the #1 priority? No access to the DOM, no access to local storage, no access to networking… WASM will continue to be borderline useless until it can actually do the things an application needs to do, without having to implement some hackjob JS interop layer.
I/O and stuff like that is being done in the WASI proposals not in WASM proper. I believe most of this stuff is waiting for initial implementations at this point and then it becomes a proper standard.
These all sound like good improvements to WASM as a binary target, but… how do we STILL not have access to any kind of I/O? How is that not the #1 priority? No access to the DOM, no access to local storage, no access to networking… WASM will continue to be borderline useless until it can actually do the things an application needs to do, without having to implement some hackjob JS interop layer.
I hate having to use js interop for simple stuff like manipulating the history stack or even just saving to the clipboard
I/O and stuff like that is being done in the WASI proposals not in WASM proper. I believe most of this stuff is waiting for initial implementations at this point and then it becomes a proper standard.