19 ms·
Unless you've already internalized how this stuff works, ShaderToy code is pretty incomprehensible. Some of it is commented, most of it isn't, and even then, GL
by roywiggins 9y ago
Unless you've already internalized how this stuff works, ShaderToy code is pretty incomprehensible. Some of it is commented, most of it isn't, and even then, GLSL is not a great literate coding language.
Here's an example of a blog post I wrote "repackaging" a technique:
http://roy.red/droste-.html#droste http://roy.red/droste-.html#droste
Compare to the code I'd found on ShaderToy:
https://www.shadertoy.com/view/4tlGRn https://www.shadertoy.com/view/4tlGRn
Is it interesting if you've already spent time on this particular thing? Probably not. But it's meant to be a useful introduction, not a novel work.
- biocomputation 9y ago<< But it's meant to be a useful introduction, not a novel work. Yes, except it's really a copy/paste job from learnopengl.com and other sources. It's actually not a useful introduction since it just parrots stuff that is already available on other sites.
- hackcasual 9y agoA lot of the shadertoy stuff is iteratively built making it even harder to tease apart. A sophisticated demo may contain a 3d noise function, a ray marcher, a signed distance field approximator etc... and there's nothing like library separations.