@mikehearn: I hope you will be more convinced at the end of the year 😉 I think WebAssembly is the result of many previous attempts : native client, asm.js, GWT, Dart but also Java applets, Flex, Haxe, etc. A lot of lessons have been learnt, and this time it seems the big ones all play together, which is really something new. MVP is mostly C/C++ centric but what will be interesting to see is what occurs post MVP. WebAssembly is not fixed in stone yet, and languages like Swift or Kotlin could significantly impact what WebAssembly will be if the catch the train now. In any case, I prefer a clean bytecode approach that exposes DOM and Web APIs (even if this is a long road) without having to transpile to JS, which is a hack full of traps ...