WASI 0.3 Ratified: Async Becomes Native to WebAssembly Components
By
Bailey HayesYosh Wuyts
17h ago· 8 min readenNews
100/100
Golden Brown
Bagelometer↗
A five-star bake. Worth schmearing, sharing, saving.
Score100TypenewsSentimentpositive
Summary
WASI 0.3 has been officially ratified by the WASI Subgroup, rebasing WASI onto the WebAssembly Component Model's async primitives. The update makes async operations native to WebAssembly Components, moving previously separate I/O functionality (pollables, input-streams, output-streams) into the canonical ABI. The changes from WASI 0.2 to 0.3 are described as mechanical and simplifying, with the specification now stable and runtime/toolchain support being rolled out.
Key quotes
· 5 pulledWASI 0.3 is official, and async is now native to WebAssembly Components.
The WASI Subgroup voted to ratify WASI 0.3.0, rebasing WASI onto the WebAssembly Component Model's async primitives.
The 0.3.0 specification is now stable, and runtime and toolchain support is landing now.
The work that wasi:io in WASI 0.2 used to do (pollables, input-streams, output-streams) is now part of the canonical ABI, where the Component Model now offers these primitives natively.
Most of the changes from WASI 0.2 to 0.3 are entirely mechanical and significantly simplify the signatures.
WASI 0.3 is official, and async is now native to WebAssembly Components. The WASI Subgroup voted to ratify WASI 0.3.0, rebasing WASI onto the WebAssembly Component Model’s async primitives. The 0.3.0 specification is now stable, and runt...
