(Ow my head) A color space is a mapping between signal values and corresponding absolute colors. References Use Wikipedia for quick reference. But use the official specs for detailed and authoritative reference (generally the first link in the Wikipedia article's References section), though they are very terse. The specs generally specify encodings, so RGB->YCbCr, leaving it to us to invert them into YCbCr->RGB decoders. We usually (but not always) say "Rec709" and "Rec2020", but you'll sometimes see "BT.709", "BT.2020", or similar. They're the same. Use whatever name other people are using.

Linearity Colors on the web are treated as perceptually linear. 50% gray appears half as bright as 100% white. However, if you interleave white and black rows of pixels, it looks like ~70% gray, not 50%. This demonstrates that having only 50% of the photons still looks 70% as bright. Keep this in mind if you are resizing anything! But the web deals in perceptual values, not physical photon counts. sRGB texture formats are an encoding, not a color space The human eye is much better at seeing small differences between dark values, but not so much for small differences between bright values. In other words, going from 5% to 15% is obvious, whereas 85% to 95% is more subtle.

(snapshot 2020-03-24 22:13 PST) WebGL is a complicated API, and it's often not obvious what the recommended ways to use it are. This page tackles recommendations across the spectrum of expertise, and not only highlights dos and don'ts, but also details why. You can rely on this document to guide your choice of approach, and ensure you're on the right track no matter what browser or hardware your users run. Address and eliminate WebGL errors Your application should run without generating any WebGL errors (as returned by getError). Every WebGL error is reported in the Web Console as a JavaScript warning with a descriptive message. After too many errors (32 in Firefox), WebGL stops generating descriptive messages, which really hinders debugging.