Live data from Hacker News

Practical Color Theory for People Who Code

tallys.github.io

41–50 of 72 posts

Re: Practical Color Theory for People Who Code

#41

If you want to do something meaningful with colors, don't use RGB, and don't use HSL (which is based on RGB). These spaces are problematic. For instance, pure blue and pure green in RGB space have very different lightness. Here's a picture of the region of colors covered by RGB: https://en.wikipedia.org/wiki/HSL_and_HSV#/media/File:Srgb-i... If RGB space corresponded to what our eyes saw, that would be a perfect hexa…

See also http://www.hsluv.org for a perceptually uniform colour space based on CIELUV.

I'm not convinced. Picking one fresh-looking color, and sliding the "H" slider, I'm running into non-fresh (dull) looking colors. Or is that somehow supposed to happen?

Re: Practical Color Theory for People Who Code

#43

Earlier quoted context omitted.

red green is bad because of colour blindness

All colors are potentially problematic. https://en.wikipedia.org/wiki/Color_blindness#Types

I once read, contrast is the key.

All colors are problematic, but if you get your contrast high enough, this doesn't matter.

Re: Practical Color Theory for People Who Code

#44
What I found really useful about this was how the presentation laid it out in a way where I could really understand it. For the first time, I got a simple set of concepts behind choosing colors. Without going back to the article, just what I remembered:

1) Choose complements. 2) Mix them with each other until they dull down a bit 3) Make some other neutral color ( possibly by mixing them in equal parts ? ) and then you have 3 colors, and you've got a basis.

( OK -- just considering is there any connection between color theory and the basis of a vector field? )

So what I liked about this was it taught me something I didn't know.

I accept there are a lot of comments by experts on here about how this simplified presentation is wrong in such and such a way. I don't think that decreases its utility for me.

To a novice, just having something tangible to understand is the first step. I understand how to experts, it seems like the wrong advice. But I felt I understood it, and that's invaluable.

If you don't know what I mean by this, maybe it's better explained by something a professor said to me in grad school, "The trick to teaching is to trick people into thinking they understand it. Don't show them all the complexity. Show them a simplified model. Let them come to it in stages."

I think that's true. It stuck with me and it seems true. It also matches what I see my science education was like looking back -- a presentation of a series of models, over a number of years, that gradually layered in more and more complexity, but at a pace that was comfortable. This "chain of models" mostly agreed with each other, but the points where they contradicted each other didn't to my memory negatively impact learning, instead they served as signposts that made each model more distinct and aided in remembering them.

Also, there is this great feeling of being able to say, "Yes from the perspective of model X that is true, but when you factor in what model Y says, you get a different picture. Here, let me show you." That always sounds like a true expert. I like that and it also seems like having a bunch of models, not all in perfect agreement, in fact strengthened by the points where they do differ, gives overall a far richer picture of the topic.

The strongest idea that stayed with me from my science education was that "everything is a model" and "none of them are true" but some of them are useful. Different models, with different levels of faithfulness to evidence.

My main critique of what I will label the "dismissive expert answers" is that they posit a inflexible model of the "absolute truth", which, I say is, given by itself: not that useful ( at least to learn the topic ), and not really true ( because well, no model can be ).

I am sorry if this length comment is more suited as a blog post. Maybe I should just make blog posts instead of comments and link to the article. Maybe that's better than anyone. I'm not trying to offend any experts or do anything ego based, just push back against the what I feel were dismissive answers that missed another side of the value of this article. I wanted to share what I thought that other side of the value of this article was.

It does seem like a highly personal comment, just from my point of view. I hope it's been useful to some others to read it!

Re: Practical Color Theory for People Who Code

#45

Do you guys know of any solid guides on how to use and mix and match colors in photography and video making to evoke certain specific emotions? It's easy to find materials on entry level color theory "here are complementary colors, here is a triad etc" but I haven't been able to find a good resource on how to use those coloring choices to influence viewer reactions. Seems like something everybody in the visual arts e…

[deleted]

Re: Practical Color Theory for People Who Code

#46
She makes excellent points in the text, but then uses less-than-optimal colours to back up her points. There is also much, much more to colour theory than what is outlined in this nice example.

And as others pointed out HSL/RGB are not the best (or easiest) to do heavy colour-theory based deesigns. If you're serious about colour theory in design, use CIE Lab* or Munsell

Re: Practical Color Theory for People Who Code

#47
post #43

Earlier quoted context omitted.

All colors are potentially problematic. https://en.wikipedia.org/wiki/Color_blindness#Types

I once read, contrast is the key. All colors are problematic, but if you get your contrast high enough, this doesn't matter.

A more reliable and helpful approach is to make sure that colors meant to convey information are augmented by some other indicator (symbols/shapes, text labels, line styles, etc.) whenever possible. In addition to avoiding colorblindness issues, this makes the difference easier to recognize in general. It also helps accommodate non-ideal viewing conditions such as a washed-out display, coordinating between displays that are calibrated differently, monochrome print/e-ink, and so on.

Re: Practical Color Theory for People Who Code

#48
post #41

Earlier quoted context omitted.

See also http://www.hsluv.org for a perceptually uniform colour space based on CIELUV.

I'm not convinced. Picking one fresh-looking color, and sliding the "H" slider, I'm running into non-fresh (dull) looking colors. Or is that somehow supposed to happen?

What sort of computer are you viewing it on? On my mac and ipad the colours work very predictably, but on my work Linux box (which has absolutely no colour calibration) I see huge changes round the red and purple areas of the h slider.

Re: Practical Color Theory for People Who Code

#49
post #41

Earlier quoted context omitted.

See also http://www.hsluv.org for a perceptually uniform colour space based on CIELUV.

I'm not convinced. Picking one fresh-looking color, and sliding the "H" slider, I'm running into non-fresh (dull) looking colors. Or is that somehow supposed to happen?

In a sense, yes. The true "freshness" of a color is shown on the color picker as the distance from the center of the circle. This is equivalent to the chroma component of CIELUV, the color space that HSLuv is based on. The problem with that component is that the maximum chroma is different for different hues, so if you were to move the hue slider while keeping true chroma static, you would run into impossible colors (such as dark saturated yellow).

This is a fundamental trade-off. If you need true saturation, you can use CIELUV and deal with impossible colors. If you need a color space that doesn't have gaps, use HSLuv and deal with a suboptimal saturation. The strongest claim I can make about HSLuv's usefulness is that it is a better HSL.

Hope that helps.

EDIT: You gave an idea that it would be useful to show another slider on the picker called "C", showing the chroma component with gaps.

Re: Practical Color Theory for People Who Code

#50
post #41

Earlier quoted context omitted.

I'm not convinced. Picking one fresh-looking color, and sliding the "H" slider, I'm running into non-fresh (dull) looking colors. Or is that somehow supposed to happen?

What sort of computer are you viewing it on? On my mac and ipad the colours work very predictably, but on my work Linux box (which has absolutely no colour calibration) I see huge changes round the red and purple areas of the h slider.

I'm on Linux.
Post reply on HN