[FoRK] WebAssembly | Luke Wagner's Blog

Dr. Ernie Prabhakar drernie at radicalcentrism.org
Sat Jun 20 22:18:39 PDT 2015


Drool. If this had been around a year ago, I would’ve built my startup around this...

> https://blog.mozilla.org/luke/2015/06/17/webassembly/ <https://blog.mozilla.org/luke/2015/06/17/webassembly/>
> 
> WebAssembly
> 
> I’m happy to report that we at Mozilla have started working with Chromium <https://twitter.com/jfbastien/status/611201861245399041>, Edge <http://blogs.msdn.com/b/mikeholman/archive/2015/06/17/working-on-the-future-of-compile-to-web-applications.aspx> and WebKit <https://bugs.webkit.org/show_bug.cgi?id=146064> engineers on creating a new standard, WebAssembly, that defines a portable, size- and load-time-efficient format and execution model specifically designed to serve as a compilation target for the Web. As reflected in the high-level goals <https://github.com/WebAssembly/design/blob/master/HighLevelGoals.md>, a central requirement for WebAssembly is that it integrate well with the rest of the Web platform and that the initial version <https://github.com/WebAssembly/design/blob/master/MVP.md> run efficiently on current browsers using a client-side polyfill <https://remysharp.com/2010/10/08/what-is-a-polyfill/>. As demonstrated <https://github.com/WebAssembly/design/blob/master/FAQ.md#can-the-polyfill-really-be-efficient>, the polyfill can leverage asm.js to get great performance. For existing Emscripten/asm.js users, targeting WebAssembly will be as easy as flipping a flag <https://github.com/WebAssembly/design/blob/master/FAQ.md#whats-the-story-for-emscripten-users>. Thus, it is natural to view WebAssembly as the next evolutionary step of asm.js (a step many have requested and anticipated).
> 
> 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 <https://www.w3.org/community/webassembly/>, some initial prototyping and early cross-browser consensus on the high-level design documents <http://github.com/webassembly/design/>. Going forward, there will be a lot more iteration and experimentation under the WebAssembly <http://github.com/webassembly> GitHub organization. For questions, check out the still-emerging FAQ <https://github.com/WebAssembly/design/blob/master/FAQ.md>. Brendan Eich also has a vibrant blog post <https://brendaneich.com/2015/06/from-asm-js-to-webassembly> with more context, history and JS perspective.
> 





More information about the FoRK mailing list