Blow’s example is using the GPU to draw pixels. Your counter was, “... it seems it’s out of reach for web developers”. If you want to use hardware graphics acceleration, use WebGL (https://developer.mozilla.org/en-US/docs/Web/API/WebGL_API …). It’s not out of reach. https://package.elm-lang.org/packages/elm-explorations/webgl/latest …
-
-
Well then Jonathan's point is moot. Web developers make web sites.
1 reply 0 retweets 1 like -
I think the point that he’s attempting to make is that web developers could make better performing web sites if there was better understanding of hardware and if APIs were used to take advantage of that hardware, i.e. WebGL. I’m not entirely sure though. That’s how I read it.
1 reply 0 retweets 0 likes -
WebGL is used to make things like 3D Objects. It's pretty cool. But to suggest that devs should use 3D rendering to create a page with text and images is silly. Even if it would perform better.
1 reply 0 retweets 2 likes -
Replying to @SeventhSunDK @rastreus and
Thats the crazy thing though. I promise you it would be less dev time, less buggy, and redonkilously faster using webGL. Because then you actually have the ability to program the gpu. Native gui toolkits like GTK or qt use 3d api's like Vulkan or GL for graphics.
2 replies 0 retweets 1 like -
Replying to @SamHSmith2 @rastreus and
A big part if the internet is the ability to search for and find pages of text. Rendering everything as graphics is a fundamentally bad idea.
2 replies 0 retweets 0 likes -
Replying to @SeventhSunDK @SamHSmith2 and
What do you think happens when you draw text? How does the text become pixels on the screen? It has to happen somehow.
2 replies 0 retweets 3 likes -
Replying to @Jonathan_Blow @SeventhSunDK and
Yes but if you go full WebGL right now, you lose the plaintext that can be indexed, searched, read by screen readers and so on. You just have an opaque <canvas>.
1 reply 0 retweets 1 like -
Replying to @janiczek @SeventhSunDK and
Not if you implement those things. But, I also think WebGL is dumb and a travesty, so, this is not the route I would recommend, quite.
1 reply 0 retweets 2 likes -
Replying to @Jonathan_Blow @janiczek and
What is the route that you would recommend for developing web apps?
2 replies 0 retweets 0 likes
I am talking about removing most of the arbitrary constraints that currently limit web apps. If I were writing an individual app, I would try to design it as closely along this future pathway as possible.
-
-
Replying to @Jonathan_Blow @rastreus and
Why would the web need 60fps (if that's the future pathway you meant) at all? I think the main problem of web app is that the signal over noise ratio is too low (banana/jungle).
1 reply 0 retweets 1 like -
Replying to @litchiedev @Jonathan_Blow and
Idk, global warming? If your site has 100000 users and it takes 5 sec to load you waste 140h of peoples time assuming they only opened the app once. If you could spend 50h reducing the loading time it becomes an ethical failing not to do so. Not to mention all the E-waste you
2 replies 0 retweets 1 like - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.