React, Flux, GraphQL, Hack, HHVM...? All of this and more!
Building communications and computing technology is a painstakingly long task. The route from initial idea will typically take years first to spec, implementation and finally mainstream adoption. WebAssembly is now on this route, it is already usable - but the official specification work continues.
WebAssembly is an architecture where web developers compile binary payloadds that are executed by the browser. Instead of script format the binary format is on average smaller, and can take use of novel optimisations like streaming compilation to gain a perforemance advantage.
Any web technology needs implementations. But for WebAssembly this is looking good, the dark ages of proprietary web technologies like ActiveX and Adobe Flash are long gone. The community has learned to work together. At this early stage we've already had three implementations since early 2016:
The WebAssembly train is well on track, as tooling around Rust and other languages comes available. HTML5 underlined the need for specifications not only for web developers, but browser vendors as well. The WebComponents work and adoption has taken more time than expected, but eventually Web Components are likely to become the norm, and in the meanwhile developers are free to use technologies like React.js or Vue.js for Interfaces.
A formal specification for a technology of such low level core technology for the future of the web. WebAssembly standardization work is done by the World Wide Web Consortium (W3C). It is an community with member organisations, some full time staff and other employees. The organization is lead by Tim Berners-Lee on a mission to allow the web to reach it's full potential.
On February 15th 2018 the W3C working group on WebAssembly announced their first set of Web Assembly Drafts. The specification comes in three parts:
WebAssembly is proceeding well in four key areas that are needed for long term success of any computing platform or component: