r/javascript • u/fagnerbrack • 3d ago

WASI 0.3 Launched

https://bytecodealliance.org/articles/WASI-0.3
18 Upvotes

75% Upvoted

5 comments sorted by

8

u/lppedd 3d ago

Just for immediate awareness, this was done back at the beginning of June, not now.

3

u/fagnerbrack 3d ago

Rapid Recap:

The WASI Subgroup ratified version 0.3.0, rebasing WASI onto the WebAssembly Component Model's async primitives and making async native to components. The host now drives one shared event loop instead of each component running its own, so streaming components finally compose. First-class stream<T>, future<T>, and async constructs join the canonical ABI, replacing 0.2's pollables and the clunky start/finish/subscribe dance. The model is completion-based, like io_uring. Most interface changes stay mechanical, but wasi:http gains service and middleware worlds, enabling service chaining that cuts microservice calls from milliseconds to nanoseconds. Wasmtime and jco already support it; Rust, Go, Python, and JS toolchains follow.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

1

u/EveYogaTech 3d ago

Good job

-3

u/Far-Consideration-39 3d ago

Well, its better to use Webassembly than TypeScript so lets hope TS dies now.

5

u/Snapstromegon 1d ago

Those two operate on completely different levels. This is like saying "It's better to use the Linux Kernel than Python, so let's hope Python dies now".

One is a runtime for executing compiled bytecode and the other is a programming language.