That’s interesting! Can you say a little more? I find jq’s syntax and semantics to be simple and intuitive. It’s mostly dots, pipes, and brackets. It’s a lot like writing shell pipelines imo. And I tend to use it in the same way. Lots of one-time use invocations, so I spend more time writing jq filters than I spend reading them.
I suspect my use cases are less complex than yours. Or maybe jq just fits the way I think for some reason.
I dream of a world in which all CLI tools produce and consume JSON and we use jq to glue them together. Sounds like that would be a nightmare for you.
This is a pretty weak argument. Blaming the two-party system might feel good, but I don't think it gives us a better understanding of what happened in this election. People voted for the guy at the top of the ticket, and he was pretty clear about wanting to get rid of some federal agencies. I think we have to conclude that people were receptive to his message.
My hot take is that the two-party system isn't anywhere near as bad as people think it is. In countries with multi-party systems, parties often have to form coalitions in order to govern. In countries with two-party systems, parties have to do most of that coalition forming before the election. That's why we see far-left and center-left politicians in the Democratic party instead of having viable left wing parties.
One way or another, we get a coalition government. Is it better for those coalitions to be formed before the election or after? If it happens before the election, the electorate can see the results in time to change their decision. If it happens after the election, the fringe parties' arguments probably get discussed more, but there's no guarantee those parties will be part of the governing coalition.
I suspect my use cases are less complex than yours. Or maybe jq just fits the way I think for some reason.
I dream of a world in which all CLI tools produce and consume JSON and we use jq to glue them together. Sounds like that would be a nightmare for you.