grc VS humanlog

Probably not as efficient, but I've been happily using grc [0] for the past several years. It handles simple rules quite well - beyond the basic info/debug/error coloring I use it for QOL such as different colors for even/odd timestamps and highlighting decimal places in large numbers.

[0] https://github.com/garabik/grc

A fairly simple program which only colorizes is grc. I wrote acolor in a similar vein, but it uses arbitrary programs/scripts instead of pure regex, and I've only written support for the programs I use, so no tcpdump. Don't use it unless you want to write your own colorizing scripts (if you do, please contribute!)

You may want to check https://github.com/garabik/grc

You'll probably appreciate grc.

There's this, which is a more modern dig, with color output, among other things: https://github.com/ogham/dog

There's also stuff like this, which will postprocess & color output from any command: https://github.com/garabik/grc, or https://github.com/armandino/TxtStyle

I also found grc and wrote my own conf.latexmk:

Conversely if you want to add color to a command, I have found Generic Colorizer to be useful: https://github.com/garabik/grc

Last few streams I was working on a re-implementation of grc with more modern Python syntax and updated packaging meta-data.

I also think there's a lot more that can be done if your focus is on "human readable" beyond just "logging with colors". I've played around with this myself while trying slog on for size and inspired by humanlog. Things like visually distinguishing the message, while also visually minimizing the timestamp with color and marking keyvals differently to the main message and even allowing for indentation and grouping of output are important considerations when you know you have a TTY and don't care about being machine-readable or even particularly fast. In that regard, I think that charmbracelet/log could be doing more.