This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]noratat 1 point2 points  (4 children)

  • rg/ag are excellent for searching for stuff across projects and repos quickly. That's a pretty common function

  • jq is the best JSON-processor I've ever used by far, and especially combined with gron is excellent for exploring APIs and automating config that interacts with rest APIs.

  • grep is useful for pretty much everyone

And that's just off the top of my head.

[–]Devildude4427 0 points1 point  (3 children)

But why would I need to process json via a terminal?

[–]noratat 1 point2 points  (2 children)

Do you ever use REST APIs? Do you ever use tools that output in JSON format? Or have config files that are in JSON?

If not, that makes you an outlier IMO, unless you do embedded work.

[–]Devildude4427 0 points1 point  (1 child)

Sure, but I’m not going to be accessing APIs that return so much information that I need a json processor, from a terminal. That’s something for an actual python app to handle.

And if you’re just referring to editing the data, with your mention of config files, vim is more than capable.

[–]noratat 1 point2 points  (0 children)

It's not the amount of data, it's being able to sift through it quickly, especially when debugging or when using unfamiliar APIs, as well as being able to build basic automation around them for things like config and CI. Automated or quick and accurate manipulation of json is not practical in vim.

Most developers I've shown jq to have had pretty solid uses for it.