Re:Bounties Damage Open Source Projects
by slimsag on Sunday September 17, 2023 @10:56AM
(#37545670)
I'm glad your communication with them in the aftermath was respectful.
Good that came out of your behavior, though: I learned that the Bytecode Alliance is just really bad at communicating historically, but has been trying to improve that and actually has been pushing forward WASI preview 2 quite aggressively, making a ton of progress on it.
Someone linked me this roadmap video[0] in which they say:
* WASI Preview 2 ships by the end of the year and is largely usable now
* Two people are working on WASM threads
* VMWare has been working on Garbage Collection in wasmtools, and is working on getting that running in wasmtime
* Components are isolation units for threads, memory space, etc. It means a WASM module can use components without being aware of threads. Components are named, versioned, etc.
* They're considering resource and handle types (I assume for e.g. externalized file handles)
* Once WASM GC moves forward, it will also go into components.
* WASI sockets, WASI HTTP, clock, filesystem, RNG are all in scope for WASI preview 2 around Fall.
* wasmtime and a JS web implementation are in scope, so two implementations of all this.
Sounds quite promising compared to what was happening in the past! Now I wonder why WASIX is a thing instead of pushing forward with WASI given they've been changing for the better?
Good that came out of your behavior, though: I learned that the Bytecode Alliance is just really bad at communicating historically, but has been trying to improve that and actually has been pushing forward WASI preview 2 quite aggressively, making a ton of progress on it.
Someone linked me this roadmap video[0] in which they say:
* WASI Preview 2 ships by the end of the year and is largely usable now
* Two people are working on WASM threads
* VMWare has been working on Garbage Collection in wasmtools, and is working on getting that running in wasmtime
* Components are isolation units for threads, memory space, etc. It means a WASM module can use components without being aware of threads. Components are named, versioned, etc.
* They're considering resource and handle types (I assume for e.g. externalized file handles)
* Once WASM GC moves forward, it will also go into components.
* WASI sockets, WASI HTTP, clock, filesystem, RNG are all in scope for WASI preview 2 around Fall.
* wasmtime and a JS web implementation are in scope, so two implementations of all this.
Sounds quite promising compared to what was happening in the past! Now I wonder why WASIX is a thing instead of pushing forward with WASI given they've been changing for the better?
[0] https://www.youtube.com/watch?v=Yl_O95zOJbs