by clebio on 12/12/21, 6:24 PM with 26 comments
by wodenokoto on 12/12/21, 9:58 PM
by junon on 12/12/21, 9:12 PM
by vanderZwan on 12/12/21, 11:26 PM
Whenever I try to learn WebGL (or similar technology) I give up after a while. In my head I imagine it as if the entire automotive industry was only aimed at F1 race cars, and people who want to do practical day-to-day things with cars only had F1 tech to work with, including the cost and complexity.
by davedx on 12/13/21, 12:14 PM
Having done a decent amount of games development, and a little bit of shader coding, the pain points fixed by the approach in the article are significant. Really impressive stuff.
I didn't even realize it was going to be TypeScript until much later in the article too, that was the cherry on top :)
by inDigiNeous on 12/13/21, 6:50 AM
Many times it would be better to have a simple way to express ideas, not having to deal with the most performant systems, which might take a lot more figuring out or issues with debugging your shaders.
by onion2k on 12/12/21, 10:09 PM
by perceptive on 12/13/21, 7:39 AM
by aappleby on 12/13/21, 1:51 AM
For toy apps, sure. For professional apps or games, abso-frickin-lutely not. Shader compilation jank is still an annoying issue in even recent games, and even having the ability_ to define arbitrary shaders at any point is such a huge footgun that I'd never let it past code review.