Yeah, I see JQ as the grep/sed of JSON. If there were a curl-analogue that constructed HTTP requests from its output, it would take me a lot of the way there.
But more generally, I'm dealing all the time with a hodgepodge of json, csv, yaml, POM files, git logs, whatever. We need more tools that understand the semantics of data.
But more generally, I'm dealing all the time with a hodgepodge of json, csv, yaml, POM files, git logs, whatever. We need more tools that understand the semantics of data.