Since jq is sed for JSON, by the transitive property, you're saying that sed is not Unix-y. ;) Seriously though, I use both, and IMO they serve different purpo

Since jq is sed for JSON, by the transitive property, you're saying that sed is not Unix-y. ;) Seriously though, I use both, and IMO they serve different purposes. gron is incredibly useful for exploring unknown data formats, especially with any form of something | gron | grep something Once you've figured out how the data format in question works, a jq script is usually more succinct and precise than a chain of gron/{grep,awk,sed,...}/ungron. So in practice, gron for prompts and jq for scripts.