2015-06-01, 11:20
Shadertoy is meant to be a simplistic way to test out shaders. That people are able to do this insane stuff with the API is just cool. Normally you'd mix and use other stuff to achieve it with better performance, but to do that you'd need a full game engine In the shadertoy visualizer the majority of the code is audio related and not graphics, this is because how simplistic the engine and the API is.
My hopes is to find some more time to fix up dawn, which is inspired by three.js, which is closer to an actual graphics engine. With that and the stuff I have in shadertoy it should be much easier to actually make visualizers that perform, but with more implementation time. Its always a tradeoff
Consider shadertoy viz more of a fun thing, it was never meant to run on all hardware. The reason I did it was that it needed very little c++ implementation to get access to a bunch of fun vizualisations, even if they are very heavy to render
My hopes is to find some more time to fix up dawn, which is inspired by three.js, which is closer to an actual graphics engine. With that and the stuff I have in shadertoy it should be much easier to actually make visualizers that perform, but with more implementation time. Its always a tradeoff
Consider shadertoy viz more of a fun thing, it was never meant to run on all hardware. The reason I did it was that it needed very little c++ implementation to get access to a bunch of fun vizualisations, even if they are very heavy to render