4 ms·
AFAICT, it's basically xpath applied to json. Which isn't helpful, but perhaps explains why it's so obtuse.
by jldugger 6y ago
AFAICT, it's basically xpath applied to json. Which isn't helpful, but perhaps explains why it's so obtuse.
- de_watcher 6y agoAnd I still have no idea why jq is slow af.
- IshKebab 6y agoSeems pretty fast to me considering it is reading JSON. JSON is difficult to read quickly.
- lucideer 6y agoI know xpath pretty well, and cannot wrap my head around jq's DSL. It might have borrowed from elements of xpath's more obtuse expressions, but simple xpath seems much simpler (to me) than simple jq.