Jq – A Command-line JSON processor
Report a link problem
Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
Top comments
jq is awesome, a real achievement. At the same time it demonstrates everything that is wrong with traditional shells and what PowerShell gets so right. jq is not a "Unixy" tool in the sense that it should do one thing and do it right. jq implements its own expression language, command processor complete with internal "pipelines". Why would a tool need to do that? find is another utility that does many, many other things than to "find" items: It executes…
jq is written in portable C, and it has zero runtime dependencies. Thank you! When I clicked on the link I was fully expecting it to be written in Node and I was going to cry.
Considering the amount of json around, wouldn't it be time to settle on a standard for : - schema definition ( using something like typescript ? ) - data path ( similar to xpath ) - data transformation ( similar to xslt ) i'm pretty sure many people have done their things but i'm still waiting to see a tool like wsdl - based stub generators that would work on many json api. ps : i know that things like…
I’ve found that jq is great for quick one-offs. But it also has a very rich syntax that allows for more complicated use cases. That said, instead of heading for the jq manpage I find it’s much easier to hack something together in Python. What’s the draw of jq here? The ability to parse with only a command line?
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
HN stats
- Breakout years
- 3
- Total points
- 847
- Total comments
- 178
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking