4 ms·
A lot of people here are attributing semantics to the article that I don't believe it has claimed. To me this simply reads, "If your application deals with col
by tpoacher 3y ago
A lot of people here are attributing semantics to the article that I don't believe it has claimed.
To me this simply reads, "If your application deals with colour, consider your user, and please also consider this standard".
In particular the line "If your software outputs colour by default, please consider not doing so", on one hand comes across as opinionated, on the other hand I mostly interpret this as a call to not have coloured output as a default without having first considered an easy way to disable it, which is sensible.
I like colours in my terminal, and have included them in most of my non-trivial work; I have also added NO_COLOR because I think it's a nice informal standard, but more importantly I support the --color=<auto|never|always> GNU standard.
The part where I lack a bit is the customisability; I'm not too sure how to use terminal themes, so I have been using absolute colour sequences instead. I need to look that up...