News for hackers. Stuff that matters.
Re:WASIX, the Superset of WASI Supporting Threads, Processes... by 5- on Tuesday May 30, 2023 @01:39PM (#36127881)
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.

Re:WASIX, the Superset of WASI Supporting Threads, Processes... by dbfa on Tuesday May 30, 2023 @01:57PM (#36128145)
WASI has been in Preview1 for a couple of years now, indeed. However, Preview2 is well underway and the initial implementation is scheduled to land in wasmtime this June.

https://github.com/bytecodealliance/wasmtime/issues/6370

Re:WASIX, the Superset of WASI Supporting Threads, Processes... by tokera on Wednesday May 31, 2023 @12:59AM (#36134631)
we also need:

- 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

please let us all know when these above missing capabilities will be delivered in preview2? will that also be in June?

honestly - we are better together - so we should find a way of bringing these dreams together going forward.

Re:WASIX, the Superset of WASI Supporting Threads, Processes... by tokera on Wednesday May 31, 2023 @12:54AM (#36134604)
(WASIX insider)

lets reflect on this - if this was done as pull requests to `preview1` then would they have been accepted?... of course not, likely with dismissive rejection comments around even the idea of suggesting some of these POSIX compatible syscalls.

WASIX should be seen as a preview1.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 (who have made comments in this thread) 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 - only 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.