4 ms·
This is lovely, but it mostly just reminds me of how I can't wait until WebGL is so commonplace that we can finally ditch all that HTML/CSS nonsense.
by skrebbel 13y ago
This is lovely, but it mostly just reminds me of how I can't wait until WebGL is so commonplace that we can finally ditch all that HTML/CSS nonsense.
- kh_hk 13y ago> HTML/CSS nonsense Structured and well declared markup is no joke. If you actually refer to the common "hacks" to get demos and eye-candy stuff working, then I do agree. On the contrary, if you refer to ditching all HTML and CSS in favor of WebGL, then we're fucked.
- skrebbel 13y agoNo, I refer to bullshit like the amount of trouble you have to go through (and subsequently the amount of upvotes you get on HN [1]) if you manage to center a rectangle on the screen. Stuff like that. It's 2013, the web is the application platform of today, and centering a rectangle is nontrivial. What? It's just one of the many examples of how broken HTML and CSS are. I dare say that anyone who claims that HTML and CSS aren't completely broken simply has absolutely no imagination and should consider accountancy. On WebGL, we can reinvent presentation and styling entirely without sacrificing performance. Maybe keep parts of HTML, and ditch CSS entirely in favour of something better, and use a JS lib to render it all on GLES hardware, the same in every browser. Designers can think about different devices and screen sizes, and not about ways of telling a browser that a div is secretly a table cell so that it can be centered. We now have many competing programming languages, competing frameworks, and so on, with a few mainstream ones and improvements/replacements all the time. Rendering entire websites in WebGL enables having the same world-wide innovation in presenting web sites and web apps to users. But even if you don't think going all-in on WebGL is a good idea, you have to agree that HTML/CSS is a gigantic 💩[2]. [1] https://news.ycombinator.com/item?id=6191350 https://news.ycombinator.com/item?id=6191350 [2] http://www.fileformat.info/info/unicode/char/1f4a9/browsertest.htm http://www.fileformat.info/info/unicode/char/1f4a9/browserte...
- cliftonk 13y agoNot only is WebGL not declarative, but how do you handle rendering text and having the browser know that it's text? While HTML/CSS has serious compatibility and expressive issues, it's moving in the right direction very quickly. WebGL will be fantastic for gaming and visualizations, I think it is very much inferior for web pages & applications.
- fuckjavascript 13y agoEasy: provide an API for specifying text selection. Provide an API for sending things to the clipboard. You know, like every other programming platform does. It's probably about time I stopped getting irritated at how incredibly slow web development types are. There is _no_ reason for the browser to be a document browser mashed together with a distributed computing platform. Other than sheer stupidity, which there is plenty of to go around. The whole purpose of the kind of distributed computing platform that you have with asm.js, webgl etc is to build fucking applications. You know, like DOCUMENT BROWSERS.
- nxn 13y ago> On WebGL, we can reinvent presentation and styling entirely without sacrificing performance. Maybe keep parts of HTML, and ditch CSS entirely in favour of something better, and use a JS lib to render it all on GLES hardware, the same in every browser I'm not sure I follow you when you say "keep parts of HTML". Are you suggesting that we should have a canvas element that spans the entire region of the page, store the actual markup of the page hidden somewhere on the page, and then parse and render that markup to the canvas element using JS+WebGl+<some CSS alternative>? Or are you saying that the browser should simply give up on rendering HTML markup, and give it over to your JS App which will render it itself using WebGL? > We now have many competing programming languages, competing frameworks, and so on, with a few mainstream ones and improvements/replacements all the time. Rendering entire websites in WebGL enables having the same world-wide innovation in presenting web sites and web apps to users. If the rendering is done in user/app space, I find it hard to believe there would be any uniformity at all. Everyone would end up having their own unique dialect of HTML that behaved and displayed differently in their own customized WebGL based rendering engine. EDIT: Disregard that last bit, I misread what you were saying to imply that it would be more uniform than what we have now.
- mbell 13y agoYa'll seem to be arguing apples and oranges. To get to the point, when webGL is commonplace what stops you from creating a 'structured and well declared' markup / styling language that renderers to webGL without all the HTML / CSS baggage?
- maaaats 13y agoYou mean end up reinventing a browser inside WebGL?
- skrebbel 13y agoYes! That would be excellent. This way, browser innovation is not limited by 3 gigantic companies and a nonprofit or two fighting five-year political wars over how to draw drop shadows on rectangles. Webapp developers can just ship the browser (or, well, the renderer) with the application.