Skip to content

Latest commit

 

History

History
46 lines (34 loc) · 3.66 KB

roadmap.md

File metadata and controls

46 lines (34 loc) · 3.66 KB
Raw
layout
default

Roadmap

WebAssembly Consensus

WebAssembly CG members representing four browsers, Chrome, Edge, Firefox, and WebKit, have reached consensus that the design of the initial (MVP) WebAssembly API and binary format is complete to the extent that no further design work is possible without implementation experience and significant usage. This marks the end of the Browser Preview and signals that browsers can begin shipping WebAssembly on-by-default. From this point forward, future features will be designed to ensure backwards compatibility.

This consensus includes a JavaScript API and binary format accompanied by a reference interpreter. You can test out WebAssembly today using the Emscripten toolchain by following the developer’s guide and reading more on MDN. You can also explore a variety of other advanced tools.

See Getting Started to start experimenting and Feedback for how and where to direct feedback.

See this message on the community group mailing list.

Next Steps

The WebAssembly community group and contributors plan to:

  • distill the design and spec interpreter repos into a single unified specification in the spec repo
  • propose a new charter for a W3C WebAssembly Working Group
  • graduate the WebAssembly LLVM backend from experimental to stable (and update Emscripten)
  • prototype additional WebAssembly integration into browser developer tools
  • Start work on post-MVP features

Changes Since the Browser Preview

  • The binary version of WebAssembly has been frozen at 0x1 (from this point forward all new features will be added in a backwards-compatible manner, and be detected through feature-testing). To update your WebAssembly modules, upgrade to the latest version of Emscripten and recompile.

Past Milestones