For the sixth year in a row, I've had the privilege of writing an article on the state of WebAssembly (Wasm).
In this article, I start off by reviewing the WebAssembly developments during 2025. Things like Safari rounding out browser support for Exception Handling with exnref and JavaScript String Builtins, the progression of Wasm features including the recently announced WebAssembly 3.0 specification milestone, and what's happening outside the browser in areas like debugging and WASI.
The second part of the article gives some insights into what's possible for 2026.
As we saw with WebAssembly 3.0 being announced, developer tooling improvements, Wasm support from most of the top 25 programming languages, and adoption in a wide variety of areas, WebAssembly has matured to the point where it's not longer an experiment. It's ready for production.
The article can be found here: The State of WebAssembly - 2025 and 2026
In this article, I start off by reviewing the WebAssembly developments during 2025. Things like Safari rounding out browser support for Exception Handling with exnref and JavaScript String Builtins, the progression of Wasm features including the recently announced WebAssembly 3.0 specification milestone, and what's happening outside the browser in areas like debugging and WASI.
The second part of the article gives some insights into what's possible for 2026.
As we saw with WebAssembly 3.0 being announced, developer tooling improvements, Wasm support from most of the top 25 programming languages, and adoption in a wide variety of areas, WebAssembly has matured to the point where it's not longer an experiment. It's ready for production.
The article can be found here: The State of WebAssembly - 2025 and 2026