One can absolutely keep a webful experience with webassembly. But there's a huge drive of "Towards a Modern Web Stack" people who want to use Canvas and raw input processing to build their own engines, ignore the web completely & do everything themselves. https://docs.google.com/document/d/1peUSMsvFGvqD5yKh3GprskLC...
They value the web only from the developer perspective, for what they can build. The user agency of the web is irrelevant. It's such a Applet/Flash/Native vibe.
It was obvious since the beginning, WebAssembly is after all the political child out of the plugins and applet wars, Mozilla not willing to adopt PNaCL, pushing asm.js instead, and everyone agreed on WebAssembly instead.
Ironically, Chrome is the one with best WebAssembly support, and Firefox hardly matters now.
3 comments
[ 3.5 ms ] story [ 25.4 ms ] threadOne can absolutely keep a webful experience with webassembly. But there's a huge drive of "Towards a Modern Web Stack" people who want to use Canvas and raw input processing to build their own engines, ignore the web completely & do everything themselves. https://docs.google.com/document/d/1peUSMsvFGvqD5yKh3GprskLC...
They value the web only from the developer perspective, for what they can build. The user agency of the web is irrelevant. It's such a Applet/Flash/Native vibe.
Ironically, Chrome is the one with best WebAssembly support, and Firefox hardly matters now.