Interesting article. I fell in love with the possibilities of GLSL shaders ages ago and tried to incorporate them more into day to day web development.
I wrote a library that enables to "apply" a shader from a GLSL file directly to an <img> tag without any additional bootstrapping needed.
I've dabbled a tiny bit with shaders, and the only debug method I could figure out was 'paint the area/pixel red if we get to this bit of code'. Not particularly helpful, surely there's a better way!
With binary I meant 1-bit pixels; in mspaint.exe this is called monochrome bitmap. I find the distinction convenient because one dimensional color can be called grayscale or black and white. Maybe 1-bit could be called black or white.
The term doesn't originate with computers, so the mono in monochrome doesn't refer to the 1 bit, but to the one colour. One dimensional colour isn't necessarily grey so monochrome is only greyscale when referring to black and white images.
If you make a cyanotype print of a black and white image the colours are blue, white and all the blue shades in between. One colour, but it's not greyscale.
OT: Why doesn't Chromium have MathML support? It seems like the kind of feature a browser engineer would actually enjoy having in there. Is there a reason to it or did the Chromium team just not get around to implement it yet?
I wrote a library that enables to "apply" a shader from a GLSL file directly to an <img> tag without any additional bootstrapping needed.
https://github.com/paratron/shaderboy
I havent used it for some time but it sounds like its perfectly suited for projects like these monochromatic portraits :)