Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Well, for some people that’s apparently fine—an image asset format (QOI) that’s been received fairly well by this forum had its author strongly opposed for the longest time to even specifying a colorspace, let alone allowing more than one. Those people are not me and I’ve cursed them out a few times, but they are not rare.

In any case, track the spec progress here: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m...



I feel the bones of a "Falsehoods Programmers Believe About Color" forming in my head.


The {Gamma,Color}FAQ pair[1] are the traditional entries in that category, although my own experience implementing colorspace transformations is that they may be making the subject appear more complicated than it needs to be.

At the same time, I’m not sure if the “falsehoods” path is the simplest here, or if an explanatory “what is” approach would be better. There’s no end to mistaken things people get confused into believing, but the fundamentals of emissive colour are just not that hard—a (mostly) linear system can only be so complicated. In that respect I think I found the introductory part of the Matplotlib colormap talk[2] to be the most helpful source on the basics.

(There are difficult things about color, of course. But perceptual similarity does not in my opinion count as part of the fundamentals. And while the science of paint and light-matter interaction in general is basically endless, unless you’re doing print design or photorealistic rendering it’s probably not an immediate concern for you.)

[1] https://poynton.ca/notes/colour_and_gamma/

[2] https://bids.github.io/colormap/




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: