WASIX, the Superset of WASI Supporting Threads, Processes and Sockets
So, let me get this straight…WASM is a language independent byte code that runs in browsers, like “assembly but for browsers” that multiple languages can compile to instead of there only being javascript.…but that ran in a browser sandbox, and people wanted to use it in containers, so they invented WASI, which lets WASM assembly code interact with the base system, sidestepping the container of the browser; but it needs a runtime on the host system (not a browser) to run.Now this is WASIX which added more non standard extensions to WASI so that more programs can run on it.We had an entire full stack cross platform runtime (browsers) to run our code in, but instead we now need to get a new set of “low level” runtimes to run the same code for, eg. containers?Sounds a lot like java to me; byte code, runtime, “cross platform binaries”, write once, run anywhere…How is this meaningfully different?The only remarkable difference appears to be you can target it with existing c++ code?