jet VS jp

I really like jq, but I think there is at least one nice alternative to it: jet [1].

It is also a single executable, written in clojure and fast. Among other niceties, you don't have to learn any DSL in this case -- at least not if you already know clojure!

[1] https://github.com/borkdude/jet

Since starting to use jet, I haven't found anything jq could do that jet couldn't also do but with the additional feature of actually being able to read what I've done with it days later.

https://github.com/borkdude/jet

Examples of Clojure projects that compile to native:

- babashka (https://github.com/babashka/babashka)

- clj-kondo (https://github.com/clj-kondo/clj-kondo)

- jet (https://github.com/borkdude/jet)

SCI is a Clojure interpreter that allows you to evaluate Clojure code even inside of the final native binary and is used in all of the above projects.

Feel free to bug me with questions in the graalvm channel on Clojurians Slack.

For me, transforming JSON on the command line was a pain, another DSL to learn. Now, I can just use Babashka/ Clojure + one or two functions from Cheshire https://github.com/dakrone/cheshire where I need to. If I needed a standalone tool, I would perhaps reach for https://github.com/borkdude/jet by the same author, Michiel Borkent, as Babashka or use jq that everybody else would find more familiar.

alias updatePackage='/usr/share/ypkg/yupdate.py' updatePackage 1.10.3.1058 https://download.clojure.org/install/clojure-tools-1.10.3.1058.tar.gz updatePackage 0.1.0 https://github.com/borkdude/jet/releases/download/v0.1.0/jet-0.1.0-linux-amd64.zip

jq is nice, but the moment i need anything more complex than "pull this attribute out of bunch of objects" i vastly prefer spinning up an actual language runtime. or use a tool built around a language (e.g. https://github.com/borkdude/jet) rather than a language built around a tool.

I have a hard time suggesting such a thing, because I find JMESPath incredibly inferior to jq's expressiveness, but if you're in the AWS ecosystem much, you may enjoy https://github.com/jmespath/jp#readme which uses the same query language as does awscli (https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-f...). That may at least pay more dividends than keeping jq's language in your head where it will only ever be used by jq

Have you tried this utility instead: https://github.com/jmespath/jp

There’s also jp, which interprets JMESPath: https://github.com/jmespath/jp

This one has the advantage of being natively understood by aws-cli, meaning you can pass a JMESPath to an AWS call and only receive the filtered / transformed result back.