Re:WASIX, the Superset of WASI Supporting Threads, Processes...
by flohofwoe on Tuesday May 30, 2023 @12:38PM
(#36126988)
WASI (and in extension this WASIX thing) is mainly for running WASM *outside* the browser, basically what POSIX is for native code.
Re:WASIX, the Superset of WASI Supporting Threads, Processes...
by skybrian on Tuesday May 30, 2023 @01:51PM
(#36128062)
Yes, understood, but the article talks about running it in a browser.
Re:WASIX, the Superset of WASI Supporting Threads, Processes...
by garganzol on Tuesday May 30, 2023 @12:42PM
(#36127062)
Easy as 1-2-3. 'sock_listen' will return ENOPERM or something like that. The app can then decide by itself what to do - either bail out with an error message or continue to work with a somewhat restricted functionality.
Re:WASIX, the Superset of WASI Supporting Threads, Processes...
by skybrian on Tuesday May 30, 2023 @01:49PM
(#36128029)
“WASIX calls can be stubbed out in a browser” isn’t really living up to the promise of “running seamlessly in a browser.” That’s closer to “not working” than “working.”
Re:WASIX, the Superset of WASI Supporting Threads, Processes...
by anticensor on Tuesday May 30, 2023 @03:55PM
(#36129804)
More like "There is no browser I/O port corresponding to your desired WASIX call". ISA compatibility and I/O compatibility do not imply each other. As demonstrated countless times during the early days of the PC.
The supposed specification is more of an API reference and I don't really trust it to tell the developer what you can really do that works well on all platforms. It doesn't document platform-specific limitations, but I don't see it documented anywhere else either.
I also wonder about copying Unix semantics for fork and exec in a supposedly platform-independent spec. It seems like that won't work equally well everywhere.