4 ms·
What makes you think so? WebAssembly is about making it possible to compile from any language into subset of javascript (which is well JIT-table), it doesn't sa
by vetinari 8y ago
What makes you think so? WebAssembly is about making it possible to compile from any language into subset of javascript (which is well JIT-table), it doesn't say nothing about neither which layout/gfx engine the apps will use, nor about any ISA. Many want the bindings to DOM, actually.
- solarkraft 8y agoWebAssembly will make it simpler to port non-DOM UI libraries to the web, which probably some people will use - though the DOM based UI libraries are already quite strong.
- pjmlp 8y agoWebAssembly + Canvas/WebGL. http://blog.qt.io/blog/2018/05/22/qt-for-webassembly-examples/ http://blog.qt.io/blog/2018/05/22/qt-for-webassembly-example... http://platform.uno/Playground/index.html http://platform.uno/Playground/index.html
- bpicolo 8y agoWould a less-specialized rendering engine not be even less performant if trying to make web-app like things?
- pjmlp 8y agoWhat web-app like? If browser vendors don't change course in regards to WebAssembly's roadmap, Flash and Applets are back, just give it one more year to mature the eco-system.
- bpicolo 8y agoSeems unlikely. Developers are already using the DOM model outside of the browser entirely a'la Electron because in modern times it's such a productive and accessible development environment. I can't imagine we'd try to bring back the pain of Flash. What we have now is drastically more portable and a delight to use compared to that era.
- TomMarius 8y agoInstead of bindings to DOM, you can offer bindings to native API - Webassembly makes it safe. Another approach is running your app on webgl. WASM is not a subset of JavaScript at all, it has similar modularization, but that's about it.