From : Luke Wagner < : Luke Wagner < lwagner@mozilla.com



Message-ID : <CANBOb-DfUAHqa5mFZdnA+O16ZFF1ELPrLj_dR2S4Rzz7vO7Adg@mail.gmail.com>

To : public-webassembly@w3.org



WebAssembly CG members representing four browsers, Chrome, Edge, Firefox, and WebKit, have reached consensus that the design of the initial (MVP [1]) 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 [2] and binary format [3] accompanied by a reference interpreter [4]. You can test out WebAssembly today using the Emscripten toolchain by following the developer’s guide [5] and reading more on MDN [6]. The next steps will be to form a W3C Working Group, to produce a specification for the initial version of WebAssembly, and to continue iterating on future features [7] in the current Community Group. To get involved, you can join design discussions [8] and contribute [9] to the the WebAssembly GitHub project. Signed, Luke Wagner, Ben Titzer, Filip Pizlo, and Abhijith Chatra P.S. We are also happy to announce the selection of the official WebAssembly logo [10]! [1] http://webassembly.org/docs/mvp/ [2] http://webassembly.org/docs/js/ [3] http://webassembly.org/docs/binary-encoding/ [4] https://github.com/WebAssembly/spec/tree/master/interpreter [5] http://webassembly.org/getting-started/developers-guide/ [6] https://developer.mozilla.org/en-US/docs/WebAssembly [7] http://webassembly.org/docs/future-features/ [8] https://github.com/WebAssembly/design/issues/ [9] http://webassembly.org/community/contributing/ [10] https://github.com/WebAssembly/design/issues/980