Re:Web Assembly and Go: A look to the future
by backpropaganda on Sunday June 24, 2018 @05:57AM
(#17385839)
Would 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)`.
Sure. 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.
Re:Web Assembly and Go: A look to the future
by backpropaganda on Monday June 25, 2018 @02:41PM
(#17394633)
But 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.
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.