3 ms·
I'm wondering about platform limitations. A web browser doesn't actually let you listen on an arbitrary socket, so how does that work? The supposed specificati
by skybrian 3y ago
I'm wondering about platform limitations. A web browser doesn't actually let you listen on an arbitrary socket, so how does that work?
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.
- flohofwoe 3y agoWASI (and in extension this WASIX thing) is mainly for running WASM *outside* the browser, basically what POSIX is for native code.
- skybrian 3y agoYes, understood, but the article talks about running it in a browser.
- garganzol 3y agoEasy 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.
- skybrian 3y ago“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.”
- anticensor 3y agoMore 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.
- deleted 3y ago[deleted]