DEV Community

Discussion on: Must have command line tools!

Collapse
 
gypsydave5 profile image
David Wickes

TBH the only useful tool in this lot is jq - it's useful for breaking down blobs of JSON in a shell pipeline. No other real alternative.

The rest of them are for developers who want the warm happy glow of working on the command line, but don't actually want to learn how to use it properly.

Collapse
 
flrnd profile image
Florian Rand • Edited

Don't be a lemon David! You are half right. I've been using cli tools since 1995. Awk, sed, ack, find... Are you one of those Who dictate which is the proper way of using things? Because in my opinion tools are there to fix problems, not create new ones 😜

Collapse
 
rhymes profile image
rhymes

ripgrep makes a real difference, especially with a large codebase. I'm not surprised VSCode integrated it for its search. I can literally see the difference between grepping with ripgrep and grep on the DEV's codebase. BTW they kind have the same options so there's no re-learning there.

I've aliased exa to ls and forgotten about it.

I've ditched httpie because it's completely different from curl.

I use hub everyday because I review tons of PRs and it saves a lot of typing :D

I tried bat for a while months ago but it's not that useful so I ditched it.

The rest seem very specific, not particularly interesting :D

Collapse
 
flrnd profile image
Florian Rand

Hey @rhymes , yeah, ripgrep is wonderful.

I use httpie because of its simplicity but not as substitution of curl. In my opinion, in terms of versatility curl is ahead of httpie.

tig and ranger are a nice addition, but I admit that I don't use them a lot.

I tried exa but after a few hours found the coloured output annoying. Weird, I know.

But I agree, depending on your background and needs, some of them can be more interesting than others, or not interesting at all.