3 ms·
In my experience, color is used to convey information for quick scanning, and is solid human-centered design. Developers are human too, surprisingly, and benef
by tomrod 5y ago
In my experience, color is used to convey information for quick scanning, and is solid human-centered design.
Developers are human too, surprisingly, and benefit from good UX!
I'm a bit surprised a seasoned programmer feel these design patterns and tools for humans is childish. Do Visual Studio/C# coders typically see the many different universes of tooling outside of the limited MS Stack as childish or less evolved?
- jiggawatts 5y agoThe differences is that a cohesive, consistent UI like the Visual Studio IDE allows complete customisation of the color scheme, uses subtle queues, and has colours that make sense in the context. Typical open source command line tools are written by random people from all over the place, and there is no consistency at all, except perhaps seeing orange for warning and red for error. All other bets are off. It's not like PowerShell, where there's separate output streams for Debug, Verbose, Information, Console, Warning, Error, and Progress! Where those can be styled consistently by the terminal, instead of the l33t coder that sprinkled some random Christmas lights into the output of his "xvtj7" tool or whatever. The reason "NO_COLOR" makes sense and is needed is because color in Linux-style tools is done at the wrong layer, in the wrong way. Format and style the output as the last step, not first.
- codeflo 5y ago> Do Visual Studio/C# coders typically see the many different universes of tooling outside of the limited MS Stack as childish or less evolved? Don’t extrapolate too much from N=1. I used to work in a shop that mainly uses Microsoft technology. From those dozens of engineers, I don’t think I’ve ever heard that opinion. I would say the opposite, my impression was that most of them were quite happy with the increasing Unix-ification of Microsoft’s stack.