Hacker News new | ask | show | jobs
by myaccountonhn 880 days ago
I’m probably on the wrong side of history, but I just don’t like how much color there is in modern cli tools. It is distracting
6 comments

Well, in most casees you can configure it and back in all black and white\green if you want to.

Having 8 (or more) colors help when dealing with information though, at least when you need to get a quick result and not just dig into the man pages.

I’ve mostly done that, though some apps use one color for foreground and another for background, where it doesn’t work.
Fair enough but the usefulness of a tool like this is not the colors it's the additional context at the prompt
When everything is one big screen full of white text, I find it very difficult to visually parse out, separate, and focus on information. Colors help guide your eyes and provide context. They can certainly be overused, however.
I like some colour but some tools take it way too far. As for emoji, the appropriate amount of them in a CLI tool is zero.
Why? I don't think emoji are necessary, but they are just Unicode characters; the only objection I can think of is that they are "too playful", but if our OSS CLI tools, written as a labor of love in our spare time, have to be "serious", we are utterly fucked. Unix hacking has never worn suits and ties.

Unless we are talking about unicode support. Indeed, the software should make a basic inquiry to see if the shell/terminal emulator supports unicode and fall back to ASCII if not. But there is a difference between "I don't support unicode" and "my unicode support is broken": the latter needs fixing, and emoji are actually a good test case to see if you really support unicode.

if the color conveys something meaningful then its good (imo of course)
is red on error, no color on success (of the last command) also too much?
A little bit, as I find that it can make me lose my trail of thought. Red errors for LSP or because something is wrong in the executed command is great though.