Chapter 4. Upcoming Features and Proposals
The initial release of WebAssembly in 2017 was intended to be a Minimum Viable Product (MVP). The team that worked on this project wanted to get something released quickly in order to gain traction with the community. As a result, a number of features that the team was interested in didn’t make it into the MVP “cut.”
After the initial release, the specification and process that governs WebAssembly was moved into the World Wide Web Consortium (W3C) standards organization, with future WebAssembly development adopting a similar approach to JavaScript and other web standards. There isn’t going to be a WebAssembly v2.0 with an eye-catching and tantalizing list of features; instead, new features, in the form of specifications, are developed by both community groups and vendors. These features are eventually implemented by browsers after they become sufficiently mature.
The WebAssembly standardization process adopts a phased approach, comprising phases from 1 (immature) up to 5 (standardized), with browsers typically starting to implement features in phase 3 and above. These features differ significantly in their scope and goal, and as a result they will progress through these phases at quite different rates.
This chapter does not provide an exhaustive analysis of all the currently proposed features, a number of them are really only of interest to people who are writing WebAssembly compilers. Instead, we take a look at the proposals that significantly ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access