WASI 0.3 lands native async — and one runtime, no browser, breaks the old WASI again (bytecodealliance.org)
WASI 0.3, ratified June 11, replaces the old polling primitives with first-class stream<T>, future<T> and async functions, moving to completion-based scheduling like io_uring. One event loop, managed by the host, is shared by all components.
The Wasmer CEO's reality check in the thread: it runs in one server-side runtime, no browser support, and it again breaks compatibility with the original WASI — and a decade in, skeptics still ask whether WebAssembly has had its breakthrough.
Sign in to save