1) refuses to operate on stdin; requires a filename argument, which is so irritating.
2) doesn't accept values that jq accepts
% time jq -r '[expression]' < parcels | wc
365 1454 7978
jq -r < parcels 1.39s user 0.00s system 99% cpu 1.390 total
wc 0.00s user 0.00s system 0% cpu 1.390 total
% time ~/.yarn/bin/q '[expression]' parcels | wc
q: internal error, uncaught exception:
Yojson.Json_error("Line 56, bytes -1-32:\nJunk after end
of JSON value: '{\n \"OBJECTID\": 155303,\n \"BOOK\"'")
That's super weird, I think most people use jq for bash pipelines.
Probably true but I use it regularly in the automation app huginn.