Last year I posted about WebAssembly and the Bytecode Alliance. Now I’m tire-kicking about how to make it work. Wasmer is written in Rust, has its own package manager and released its first beta. All of it is distributed as WebAssembly binaries.
While the mainstream operating system producers are in favor of pooling unprofitable compiler technology to defray development costs, they may not realize that a central bytecode may cost them market share in the end by allowing upstart operating system makers like Haiku to offer as much compatibility and better performance.
There will be growing pains, to be certain. One item that came up in the thread I linked above was the monolithic memory model used by the sandbox environment. Another thing not mentioned is that Rust programming is tricky to get a grasp on. Thirdly, the current generation of WebAssembly applications are designed to run in a browser.
My questions about the Wasmer environment are as follows: Is there someone here that develops in Rust for Haiku? Are there more hiccups to the adoption of a standardized bytecode for cross-architecture development than I’m aware of? Does this seem like plausible technology for a disruption in the tech sector?