json

Nice overview of jq! You may want to say demonstration rather than illustration though. I liked jq but liked json, a similar npm package, a little bit better for simple tasks. You can find more about it here: https://github.com/trentm/json As a JS dev I tend to have node installed anyhow so I just use a shell alias to wrap ‘node -pe’ these days. It’s not really for shell scripts but it’s great for quick every day usage. Plus you can use JS if needed instead of their DSL. Here the code for the alias in my shell profile: https://github.com/KylePDavis/dotfiles/blob/master/.profile#...

Thanks! Will have to try out `jsonata`, as `jq` never clicked for me (too complex). Alternately I've been using a node.js program `json` [1] which has a basic but straightforward cli which covers 95% of my daily needs. I believe I found after trying to figure out the tool Joyent.com uses in there SmartOS sysadmin setup. Not sure if it's the exact same tool, but it's very similar. As an example, basic manipulation is just: `echo '{"age":10}' | json -e 'this.age++' #=> {"age": 11}` 1: https://github.com/trentm/json

Or this: https://github.com/trentm/json (npm install -g json).

For a similar tool written in javascript, check out json (https://github.com/trentm/json). I use both.

jq looks nice, I use another similar tool quite a lot [1]. [1]: https://github.com/trentm/json

request - https://github.com/mikeal/request jsontool - https://github.com/trentm/json mocha - https://github.com/visionmedia/mocha stream - http://nodejs.org/api/stream.html txn - https://github.com/iriscouch/txn follow - https://github.com/iriscouch/follow browserify - https://github.com/substack/node-browserify fleet - https://github.com/substack/fleet seaport - https://github.com/substack/seaport underscore - https://github.com/documentcloud/underscore node_redis - https://github.com/mranney/node_redis node-gyp - https://github.com/TooTallNate/node-gyp cookies - https://github.com/jed/cookies node-falafel - http://github.com/substack/node-falafel routes - https://github.com/aaronblohowiak/routes.js negotiator - https://github.com/federomero/negotiator marked - https://github.com/chjj/marked JSONStream - https://github.com/dominictarr/J

My time as a system administrator makes me rather fond of logging as text into files. They're simple, easy to scale, to rotate, to compress and to throw away. One variation on this theme that I read about recently is to produce log lines as JSON objects rather than more "traditional" printf-formatted text. This gives machine readability but also makes for really simple tools for extracting whatever "traditional" log lines you like. (see: https://github.com/trentm/json) You can also easily add new fields without breaking existing log parsing code. I believe I first read about logging in JSON here: http://journal.paul.querna.org/articles/2011/12/26/log-for-m...