Hm, is there any coordination between the browser world and WASI? Component Model stuff also now includes similar things, with suspending and resuming for smooth calling between sync and async components..
For some extra context, this will open up a lot of possibilities for “compile to JS” flows, because code that assumes synchronous APIs can continue to be written as such, merely being suspended by the WASM runtime. Big deal for Python in particular
Between this and typed continuations wasm is finally awesome. One of the problems with wasm pglite and sqlite was how difficult it was to plugin a vfs in js. Other problem was that there wasn’t an equivalent to demand paging huge binaries, now there is a somewhat similar feature.
Hm, is there any coordination between the browser world and WASI? Component Model stuff also now includes similar things, with suspending and resuming for smooth calling between sync and async components..
For some extra context, this will open up a lot of possibilities for “compile to JS” flows, because code that assumes synchronous APIs can continue to be written as such, merely being suspended by the WASM runtime. Big deal for Python in particular
Between this and typed continuations wasm is finally awesome. One of the problems with wasm pglite and sqlite was how difficult it was to plugin a vfs in js. Other problem was that there wasn’t an equivalent to demand paging huge binaries, now there is a somewhat similar feature.