jql

The sentiment resonates with me. Had similar thoughts a couple years ago, and wrote jql[0] as a jq alternative with a lispy syntax (custom, not Common Lisp), and I’ve been using it for command-line JSON processing ever since! [0]: https://github.com/cube2222/jql

This looks quite cool! I'm not sure though why I would use this over the original jq. However, I can definitely see the value in embedding this into my own applications, to provide jq scripting inside of them. Shameless plug: As I'm not a fan of the jq syntax, I've created jql[0] as an alternative to it. It's also written in Go and presents a lispy continuation-based query language (it sounds much scarier than it really is!). This way it has much less special syntax than jq and is - at least to me - much easier to compose for common day-to-day JSON manipulation (which is the use case it has been created for; there are definitely many features of jq that aren't covered by it). It might seem dead, as it hasn't seen any commit in ages, but to me it's just finished, I still use it regularly instead of jq on my local dev machine. Check it out

Had the same experience. That's why I've written jql[0], which puts a uniform lispy spin on CLI JSON processing. I now use it almost exclusively instead of jq. Check it out if you're looking for alternatives. And by the way, you can achieve live preview with any of these CLI tools by using fzf. This is the snippet for jql for example: `echo '' | fzf --print-query --preview-window wrap --preview 'cat test.json | jql {q}'` (substitute jql for jq or anything else) P.S.: jql might seem dead, as there are no recent commits, but it's not. It's just finished. [0]: https://github.com/cube2222/jql

Stepping just a little beyond regular ‘loop and filter’ is already difficult without consulting the manual each time — being exacerbated by the impossibility of finding those things in the manual without skimming through most of it. Making an ‘if’ for variations in the input structure is easily a twenty-minute job. Outside of the basic features, Jq's syntax is increasingly arcane and unintuitive—maybe those working with it daily do remember the ‘advanced’ stuff, but I don't. I actually collected a sizable list of alternatives to Jq: https://github.com/TomConlin/json2xpath https://github.com/antonmedv/fx https://github.com/simeji/jid https://github.com/jmespath/jp https://jsonnet.org https://github.com/borkdude/jet https://github.com/jzelinskie/faq https://github.com/dflemstr/rq https://github.com/mgdm/htmlq And there's someone else's list

I've built jql[0] as a much more uniform and simple to use alternative to jq, with a lispy syntax. It may seem dead, but it's not. It's just finished, and I'm using it daily. [0]: https://github.com/cube2222/jql

I've written jql[0], an alternative to jq with much less syntax (being lispy) and much easier to use for me. The project may seem dead to some, but I'm using it daily, it's just finished. [0]:https://github.com/cube2222/jql

fzf is also great as a live preview window for a command: echo '' | fzf --print-query --preview-window wrap --preview 'cat test.json | jql {q}' Here shown with jql[0] to write json queries and see the live output. [0]: https://github.com/cube2222/jql

For everyone pining for a Jq with a different syntax: I have a bunch of links to alternatives collected, you might want to try some of them (some may be for different things than JSON): https://github.com/fiatjaf/awesome-jq https://github.com/TomConlin/json2xpath https://github.com/antonmedv/fx https://github.com/fiatjaf/jiq https://github.com/simeji/jid https://github.com/jmespath/jp https://github.com/cube2222/jql https://jsonnet.org https://github.com/borkdude/jet https://github.com/jzelinskie/faq https://github.com/dflemstr/rq Personally I think that next time I might just fire up Hy and use its functional capabilities.

Check out jql [https://github.com/cube2222/jql] and oj [https://github.com/ohler55/ojg]

If so, and for anybody else having this wish, check out jql[0], I've created it exactly for this reason, to have the most common jq operations available in a more uniform and easier to use interface. [0]: https://github.com/cube2222/jql

I agree, jq is very advanced when everything most people want is simple json transformation and highlighting. I've made jql[0] for that reason. Check it out, it's less featureful, but much simpler with a uniform lispy syntax. [0]: https://github.com/cube2222/jql

Nice project! Though as others already said, you can use fzf very effectively to get a GUI-like experience for such tools. If you're not a fan of jq for its syntax, check out jql[1]. It too helps you to transform json files, but does so with a consistent, lispy syntax. [1]:https://github.com/cube2222/jql

As people always do in such threads, I’d too like to chime in with alternatives I’ve been a co-author of, as this is an area I’m very interested in. The first one, which is definitely close in spirit to this project is OctoSQL[1]. We too are trying to query all the things with SQL, including JSON, though we extended the idea to supporting more data sources and file formats, with the ability to mix and match in joins and subqueries. Curious what direction this project will take though, as we’re now heading for streaming sources (like Kafka) in pure SQL! A totally different one is jql[2] where I’ve been exploring more of a lispy continuation passing style based approach to a JSON query language, as I didn’t really feel like the current ones are ergonomic. If you like this, make sure to check them out too! (And all the others people will be

A project I'm using, which I'm also one of the authors of, is OctoSQL[1]. It allows you to transform and join data from different data sources (including databases like mysql, postgres, redis, and CSV or JSON files, more to come) using a familiar interface - plain SQL. Other than that, I like Exploratory[2]. And for nested JSON data I use another project of mine, jql[3] - an easier to use (in my opinion) lispy alternative to jq. (originally inspired by a hackernews comment actually) [1]:https://github.com/cube2222/octosql [2]:https://exploratory.io [3]:https://github.com/cube2222/jql