so, aside from the obvious 'embrace, extend, extinguish' angle, why was this not part of wasi proper?
it does seem like wasi has been stuck, in the outside view, for quite a while.
would welcome any comments from wasi/wasix insiders.
it does seem like wasi has been stuck, in the outside view, for quite a while.
would welcome any comments from wasi/wasix insiders.
- full Berkley socket support
- sub-process spawning, waiting
- forking
- TTY support
- pipes
- event streams
- DNS resolving
- longjmp/setjmp
without these we can't compile our favorite apps in our favorite languages
lets help get these into preview2 so that WASIX is not needed anymore but until then the community needs an interim solution that has long term support - that is WASIX's complimentary goal.
lets reflect on this - if this was done as pull requests to `preview1` then would it have been accepted?... it would have received rejection comments around even the idea of these particular POSIX compatible syscalls.
WASIX should be seen as a preview 1.5 rather than something new, just extensions to WASI that add the missing bits that are badly needed today to actual compile useful apps from various code bases.
at a minimum this is an interim solution so that app developers can just start compiling their code bases into WASM and we can all get moving forward together - no one wants a fork here.
of course the WASI maintainers are reading all this and hopefully this will be a wake up call to add these missing syscalls as a priority also into preview2 so everyone benefits - then WASIX can die and its purpose is served... but until then WASIX will get long term support so the community can proceed literally today onwards.