Argue with the palette #44
Aejkatappaja
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Every hue in cendre came out of a measurement: Planck's law for the coals, published emission wavelengths for everything else, pushed through the CIE 1931 colour matching functions into OKLCH. Lightness and chroma were chosen, because a spectral line sits far outside sRGB and has to be brought into gamut anyway.
So there are two kinds of disagreement, and only one of them is interesting.
Not interesting: the hue.
brassis 61.4° because sodium emits at 589 nm. Moving it is not an opinion about the theme, it is deleting the theme.Interesting: everything that was chosen rather than measured.
brassat L 0.838 is the brightest thing on screen andfrostat 0.600 the dimmest, because cinder, ember and brass sit within 36° of each other and separation had to be bought somewhere. Is the ordering right? Isfrosttoo far down?cinder, types takefrost, every literal takessap. A declared name is not a role, so variable and constant names stay infgand only the value takes a pigment. This is the rule people push back on most.commentat 3.32:1. Deliberately under AA. Most dark themes people keep for years land near there, and a comment as loud as the code it explains is noise. Say if you disagree, but say it with the ratio you would use instead.hard,medium,soft.frostanderrorfall under 4.5:1 onsoft, which is stated rather than hidden.Bring a screenshot and a language. "Too dim" in Go and "too dim" in TypeScript are different claims, because the two hit different rules.
Full derivation, hue by hue: https://cendretheme.com/#derivation
All reactions