.wasmfiles on the web.
I've read enough to give an instinctive, quick, probably premature, surely gut based, impression on this matter.
I'll cut the crap and throw the following bullets at you:
- having all vendors and teams instead of being a proprietary format as it has been for the .swf before, means many more developers and engineers will be involved and happy to jump in. Beside the inevitable higher amount of consequential bikeshed, pattern that reminds me every time of the joke about "How many engineers does it take to change a light bulb?", we have proofs that sometimes this kind of effort works. For instance, the biggest release of ECMAScript since the third edition just got approved and most of the people involved were from all those browser vendors.
- asm.js will soon become a widely adopted intermediate target language, since every vendor agreed on
.wasmwhich initial goal is to be compatible with asmjs code. This is huge for Web related performance!
- it will take long time, in terms of cross platform compatibility, before we'll see real-world, full
.wasmbased applications, and my only hope is that
.wasmwon't slow down the Web, since this still needs extra attention and huge amount of improvements from every browser vendor
- we've got the proof that all people involved or not in Open Source still use "Closed Source" (private) channels to make decisions about "the destiny" of the rest of the world
- it might slowly cause the beginning of JS decline once available, since JS has been reforged to be backward compatible, but a fresh new general purpose intermediate language, that could be a better target for new programming languages too, might be a better idea, over a standard that inevitably carries on quirks trying not to break what's been developed for the last 20 years online.
I'm looking forward to see progresses, and contribute as I can!