#webassembly is a pretty big deal for the Web - it provides a compact, fast-to-parse, fast-to-run binary byte code for the Web, in the right conditions. It complements #JavaScript for tasks that are CPU intensive, and facilitates porting of non-JS code bases (e.g. game engines)

To understand the basic value proposition of #WebAssembly, @linclark provided a great series of article, notably hacks.mozilla.org/2017/02/wh…

3 specs are beginning their way on the formal standardization track today. Web Assembly Core describes the low level code format w3.org/TR/2018/WD-wasm-core-… - unless you're a compiler/transpiler guru, this is probably not things you'll be dealing with on a daily basis.

Web Assembly JavaScript Interface provides the API exposed in browsers to load, run and interact with Web Assembly modules w3.org/TR/2018/WD-wasm-js-ap…

For instance, WebAssembly.instantiate(buffer, importObj); will instantiate a Web Assembly module from the buffer, and pass it importObj where it can get data or functions from the calling JavaScript.

The last document, Web Assembly Web API, is a start of a series of further integration points into the Web Platform: w3.org/TR/2018/WD-wasm-web-a… It provides at the moment e.g. a way to compile a #WebAssembly module from a streamed response.

All that work is happening in a single Github repo github.com/WebAssembly/spec/ Because that work started its incubation some time ago in #w3cCommunity Group, despite its early stage on the standardization track, it is already widely available in browsers caniuse.com/#feat=wasm

There are still plenty of further optimizations that these implementations are looking at to make Web Assembly run even better and faster