#Instagram4nerds
My findings while playing around with fragment shaders
Shader eye candy
if you do not see the image above, check if your browser supports webgl, at: caniuse.com/webgl
I'll link the resources i used as an introduction to the subject, hence this serves as an OK starting point.
After a few days of playing around using the knowledge gained from the video linked above, i was able to code what you see above. Albeit i have a background as a developer. All this is to say, tamper you expectations before getting into the subject matter, it takes some time before you make something halfway decent, and i still am not able to bring all my ideas to fruition.
You'll often times find that you accidentally create something interesting, just by faffing about with mathematical functions. On that note, you can
I use the JS libary shader-web-background by xemantic - github.com to embed shaders on my website as seen above. It's also utilized on my landing page in the background node5.net. So masive shout out to xemantic, go buy them a tea
As xemantic also points out, one of the awesome things about shaders instead of e.g. video is the miniscule file size.
To put it into perspective the gif shown above is 236 kilo bytes
While the HTML, CSS, and JS and shader reuqired to produce said page is a mere 16.08 kilo bytes
That's a 14.67x difference. This arguably just shows how horrible the GIF format is for anything but the simplest
of things, given it's lack of interframe compression. A GIF meerly consists of sequential images, as opposed to video
that uses advanced math to bring down the file size.
Shaders on the otherhand scale to be crisp on any device. Furthermore they can be interactive, morphing with user input.