On: jq 1.7

[ustolemyname]

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.

[Nullabillity → ustolemyname]

And now you've turned a JSON traversal problem into a parsing problem.. congratulations?

[spion → ustolemyname]

Or maybe jq does have some design flaws.