4 ms·
> But once you take the time to learn it, it's fine. For a short period of time, sure.. but the ecosystem evolves quickly, and often in inexplicable ways.
by akira2501 8y ago
> But once you take the time to learn it, it's fine.
For a short period of time, sure.. but the ecosystem evolves quickly, and often in inexplicable ways.
> In the majority of cases WebAssembly is just give to give the lazy an excuse to use a language they already know rather than learn something new.
Most people program in return for money, not for self-satisfaction at learning yet another single-purpose language.
> But is a dozen incompatible, competing rendering frameworks (that each site downloads separately) going to be good for the web?
How is this significantly different from where we are now?
- untog 8y ago> self-satisfaction at learning yet another single-purpose language is a weird way of describing learning the language native to the web platform. I don't see a lot of people screaming about having to learn Objective C or Swift to make iOS apps. > How is this significantly different from where we are now? Err, because the DOM is a universal standard that comes built-in to every browser? <div style='background:red'/> looks the same everywhere, with no extra code required. If you're building a new renderer from scratch you're going to have a lot more code users need to download.
- backpropaganda 8y agoWould it though? I'm guessing something like the OpenGL spec would be standardized across browsers, and `<div style='background:red'/>` would be replaced by `glClear(1.0, 0.0, 0.0, 1.0)`.
- untog 8y agoSure. Clearing the screen is one thing. But if you've done any work in WebGL you'll know that building an entire UI library with it would be a huge, huge endeavour.
- backpropaganda 8y agoBut that doesn't seem like something that should be standardized anyway. There is no one way to do web UI, and the current popular paradigm (DOM/CSS) isn't particularly good either. Going to a lower-level gives more control to web developers, and the browser could always cache popular frameworks. Now that we think about it, even with the DOM/CSS UI framework built into the browser, people still make use of libraries like jquery so library caching is something the browser needs to do anyway, WASM or not.
- menckenjr 8y agoYou see a lot of people screaming about it if they're web developers; that's why PhoneGap/Cordova, Ionic and Flutter exist.