Re:jq 1.7 released
by speed_spread on Wednesday September 06, 2023 @11:43PM
(#37414507)
Something not having alternatives doesn't make it necessarily nice. It's okay to wish for better even if you have something that works.
[ Parent
| on HN ]
Re:jq 1.7 released
by ustolemyname on Thursday September 07, 2023 @02:06AM
(#37415294)
I think in this case "better" reduces to convincing the upstream data source to not use json.
Putting that frustration on jq seems like a case of transference.
Or maybe jq does have some design flaws.
Re:jq 1.7 released
by Nullabillity on Thursday September 07, 2023 @08:35AM
(#37418005)
And now you've turned a JSON traversal problem into a parsing problem.. congratulations?
Re:jq 1.7 released
by hn92726819 on Friday September 08, 2023 @01:38PM
(#37436773)
> Something not having alternatives doesn't make it necessarily nice
Of course not, but compared to every alternative today, jq is eons better than everything else. It's conciseness, ease of use, ease of learning all make it awesome. So as of right now, it is the nicest thing to use by far.
Personally though, I don't think I do wish for better. Jq is missing nothing that I want.