According to Eich, while asm.js has worked well, the parser is a problem. “asm.js is great, but once engines optimize for it, the parser becomes the hot spot—very hot on mobile devices. Transport compression is required and saves bandwidth, but decompression before parsing hurts,” he wrote.
According to its GitHub page, WebAssembly seeks to do the following:
- “Define a portable, size- and load-time-efficient binary format to serve as a compilation target which can be compiled to execute at native speed by taking advantage of common hardware capabilities available on a wide range of platforms, including mobile and IoT
- Design to execute within and integrate well with the existing Web platform
- Design to support non-browser embeddings
- Make a great platform.”
“We’re pretty early into the overall process: There is no draft spec or even final formal standards body chosen, just a W3C Community Group, some initial prototyping, and early cross-browser consensus on the high-level design documents,” wrote Luke Wagner, a programmer at Mozilla, in a blog post. “Going forward, there will be a lot more iteration and experimentation under the WebAssembly GitHub organization.”