HN Hall of Fame Weekly email

Jq – A Command-line JSON processor

stedolan.github.io Software & code Software projects Software engineering Candidate
Screenshot of stedolan.github.io captured 2026-07-20
Page preview · captured 2026-07-20

The originally submitted URL now redirects to the address above. Updating the destination does not change the item’s HN history, Hall membership, or rank.

Resurfaced independently across 8 calendar years, with breakout response in 3 of them.

submissions
18
submitters
16
observed span
2013–2021
peak thread · 91 comments
451 pts
latest 20+ return · 2015-04-27
451 pts

Submission timeline

2007–2026

One 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.

First comments on top threads

HN comment order

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…

useerup·451-point thread·

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.

glesica·229-point thread·

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…

bsaul·132-point thread·

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.

Breakout years
3

100+ points or 50+ comments

Total points
847

reference only — not used in Hall rules or ranking

Total comments
178

reference only — not used in Hall rules or ranking

Every submission