3 ms·
It's an experience thing. Color gets in the way in many cases. You need a way to turn it off. If you can't, then when you pipe it to a text file, it turns into
by sillysaurus3 9y ago
It's an experience thing. Color gets in the way in many cases. You need a way to turn it off. If you can't, then when you pipe it to a text file, it turns into garbage.
Worse, many programs break when you start getting fancy. If you would just stop trying to add color to your node programs, stop trying to add emojis, stop trying to control the entire terminal window, then suddenly everything would work much better. If you kick off multiple processes, you can simply console.log() instead of having to set up an RPC interface to communicate with the main process. (This actually happened.) If you stop putting emojis in your error messages, then WebStorm can highlight the stack traces automatically when you run in the debugger, enabling you to jump to the stack trace just by clicking on it. This breaks when you add emojis. (Also happened.) And if you stop adding color, then you can redirect to a file without screwing things up.
In short, stop getting fancy. :)
- avian 9y agoFirst thing I usually do on a new Linux system is dial down colors in “ls”. Default colors are ridicuously distacting and most don’t convey any new information. I like directories and symlinks highlighted. But the fact that a file is a .jpg or .tar.gz is sufficiently obvious from its name, without turning my terminal into a circus. I similarly dislike the new trend of fancy command prompts. It’s a prompt, it should stay in the background.