dog VS bottom

Dog is cross platform and has some nice features, like json output.

https://dns.lookup.dog/

> As a user of the "--color" flag for the `ip` command, I'd love to see tools like dig produce more modern output

https://github.com/ogham/dog is pretty good in that regard

Alternatively, use dog (https://github.com/ogham/dog)

> dog www.readlang.com

A www.readlang.com. 1h59m16s 139.144.234.197

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

Here is link number 1 - Previous text "dog"

There's also doggo, which you can say is a bit of a dig at dog.

See also "dog" which I've been using for a while, works well. https://github.com/ogham/dog

bottom

I'd suggest Bottom as a TUI alternative to the in-built task managers - https://github.com/ClementTsang/bottom

It works on Windows also.

If anyone is looking for a "top" like, written in Rust, might have a look at https://github.com/ClementTsang/bottom

Looks like bottom with another theme

bottom - A cross-platform graphical process/system monitor with a customizable interface and a multitude of features.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.