3 ms·
At first I was a little skeptical of this tool's claims of being simpler than jq, as I struggled to understand why (for instance) they were using <> in some par
by pmoriarty 7y ago
At first I was a little skeptical of this tool's claims of being simpler than jq, as I struggled to understand why (for instance) they were using <> in some parts of their example and [] in others, but after going through their step-by-step explanation it all made sense, and it does seem very simple. A tool that simplifies things is always welcome.
- bradknowles 7y agoThe "User Guide.md" file is over 3000 lines long, comprising some 133KB. I read through about a quarter of it, before my eyes started to glaze over. I'm not convinced that I would call this "simpler" than jq.
- ak217 7y agojq is one of the most intentionally designed pieces of software I've seen. In due time, I expect it to become as ubiquitous and indispensable as ls, grep, sed and awk. The jq language could use a formal spec, but other than that jq has a sublime elegance. By contrast, this seems like one of the least intentionally designed pieces of CLI software I've seen.