It would be nice for esy to have some kind of "look and feel".
I'm no designer, but perhaps addings brackets around the debug-level as a start might be an idea for a start? Anyway, I felt it might be an idea to ask the question while I remember! 馃檪

I think that color is really good to help clarify stuff. Is there some kind of an env var or system .config setting that is the standard convention for whether or not the user prefers color? I know that @andreypopp is not a huge fan of color, but many users like their terminal output to look like a rainbow puked all over their screen. It would be nice to let users have their individual preferences.
I like to think of colours as something that leads to visual hierarchy - dim, normal and bright. Generics parts of the message could be dim, actions or anything indicative of something more important normal and data specific to project or anything very important, bright.
This way we also avoid too many colours, or colours clashing with user's terminal themes. These are the guidelines I followed with pesy.
To me it's more of a branding thing, in the end giving an eco-system a more finished/polished feel! Rust/cargo does this pretty good while keeping it toned down! 馃檪
@lessp can you show some screenshots from Cargo that you think are representative and a good balance?
Sure!

@andreypopp What do you think we should do here?
I just discovered this protocol for suppressing colors in command line applications! It's just like the convention I suggested!
Very cool. That allows tools to output colors, but people can set this env var in their shell startup to suppress them across all tools.
Most helpful comment
I just discovered this protocol for suppressing colors in command line applications! It's just like the convention I suggested!
https://no-color.org
Very cool. That allows tools to output colors, but people can set this env var in their shell startup to suppress them across all tools.