4 ms·
>having JSON as encoding format is pretty nice, any shell script could talk with it and it's eas(ier) to inspect Why do people say things like this? The only f
by juped 7y ago
>having JSON as encoding format is pretty nice, any shell script could talk with it and it's eas(ier) to inspect
Why do people say things like this? The only format unix shell can reliably understand is tab-separated value.
- 1_player 7y agoThe shell can't speak HTTP either, but all OSes ship with a command line HTTP client. My point is that in 2019 JSON is such a common format _most_ people have or should have a JSON client encoder/decoder installed in their /bin, though I'm not sure any OS ships with any by default. To be fair, I have jq installed and I have no idea how to use it.
- Spivak 7y agoI really love the jq language but I totally agree that the complexity skyrockets once you peek at the 'advanced' features because this neat little query language turns into a full programming language with io, variables, modules, functions. Very similar to AWK. If you want something that is just a good query language then I would highly recommend JMESPath. It's a little harder to grok initially but the spec is extremely detailed, comes with examples, and there's libraries for all the 'popular' programming languages. A good CLI tool that wraps the Go library is https://github.com/jmespath/jp https://github.com/jmespath/jp