4 ms·
This is a take I don't actually agree with, on it's face, but I will say that even if we assume it's true that DOM access limitations are causing stagnation, I
by catapart 3y ago
This is a take I don't actually agree with, on it's face, but I will say that even if we assume it's true that DOM access limitations are causing stagnation, I think most devs would prefer wasm to make the DOM unnecessary, rather than to couple anything tighter.
The DOM is kind of great for modeling documents, and quickly creating a form. As far as event driven design goes, it's very performant and accessible. But if you want to do anything that isn't vector graphics or form design, the entire browser stack can hold you back in varying ways.
Personally, I'm seeing a lot of potential in the wasm vector libraries, but I'm even more excited about shader-based, immediate mode guis. And honestly, the fact that you don't need a browser is a bonus, but definitely not the main selling point.
Your milage may vary, of course, but I'm very optimistic about what's coming with wasm!