> Just to clarify my understanding, none of this is free though, right? If I understand correctly, every WASI will have to be maintained to achieve and preserve feature parity as new features are added to the language or, in the worst case, a breaking change is introduced.
WASI is versioned by namespace, which is just a prefix for the modules; so v1 and v2 of WASI may in theory actually have nothing in common so the runtime needs to support that particular version of the interface.
e.g; a module compiled today with only the MVP WebAssembly features targeting wasi_snapshot_preview1 (the current version) today should continue to run just fine as long as the runtime doesn't drop support for that version of WASI.
Features in WebAssembly itself do not necessarily require a rewrite, at-least in the current specification but it depends what happens going forward.
> This may be a naive question, but this is also only for server-side code, right? Would you be making these kinds of syscalls in code you deploy to the client? Forgive me, I'm not entirely up to speed on webasm.
Browsers too; e.g a browser game or app can use standard library i/o which calls into WASI; altho my web-wasi implementation is not up to par at the moment as I'm waiting for the outcome of a proposal Emscripten's kripken put out on how to deal with async/await in browsers.
WASI is versioned by namespace, which is just a prefix for the modules; so v1 and v2 of WASI may in theory actually have nothing in common so the runtime needs to support that particular version of the interface.
e.g; a module compiled today with only the MVP WebAssembly features targeting wasi_snapshot_preview1 (the current version) today should continue to run just fine as long as the runtime doesn't drop support for that version of WASI.
Features in WebAssembly itself do not necessarily require a rewrite, at-least in the current specification but it depends what happens going forward.
> This may be a naive question, but this is also only for server-side code, right? Would you be making these kinds of syscalls in code you deploy to the client? Forgive me, I'm not entirely up to speed on webasm.
Browsers too; e.g a browser game or app can use standard library i/o which calls into WASI; altho my web-wasi implementation is not up to par at the moment as I'm waiting for the outcome of a proposal Emscripten's kripken put out on how to deal with async/await in browsers.