Fish (suggested by the article as well) is amazing. Also:
- bat (better cat),
- btm (better top),
- httpie (better curl),
- ripgrep (better grep),
- zoxide (cd with fuzzy search)
- jq (for manipulating JSON)
But honestly, lots of classics are still great: git, htop, rsync, vim, nano, …
Hello, fellow fish user! Oh, shit, am I doing the Arch thing?
Will have to check some of those other ones out.
I’ve personally replaced nano with micro, though. Find it much friendlier to use.
Interesting suggestion of btop. How does it compare to htop?
Personally I find btop really hard to glance at and see what’s happening, htop is much better for opening up and quickly checking what process is hogging CPU/RAM/IO/whatever.
I like btop better just on an aesthetic level. But they all show the same shit as far as I can tell.
Real programmers cat the data directly from /proc
Be careful not to replace bash with fish as some systems fail to work with new shell. I usually init fish/nu shells with other instruments, like alacritty and/or zellij
I’m usually a bit scornful of “bling” commands, but
batseems genuinely useful.Agreed. Many on this list, to me, seem too busy or an outright eyesore (btop). But bat does appear truly useful. I’ll be giving that one a try.
