(jsonquerylang.org)

I'm working on a tool that will probably involve querying JSON documents and I'm asking myself how to expose that functionality to my users.

I like the power of `jq` and the fact that LLMs are proficient at it, but I find it right out impossible to come up with the right `jq` incantations myself. Has anyone here been in a similar situation? Which tool / language did you end up exposing to your users?

1. jawns ◴[27 Oct 25 17:17 UTC] No.45723690[source]▶

>>45722826 (OP) #

I'd like to know how it compares to https://jsonata.org

replies(4): >>45723858 #>>45724368 #>>45725041 #>>45731670 #

2. Alifatisk ◴[27 Oct 25 17:29 UTC] No.45723858[source]▶

>>45723690 (TP) #

Can't you just visit both pages, build an understanding and compare them?

replies(1): >>45724023 #

3. OrderlyTiamat ◴[27 Oct 25 17:41 UTC] No.45724023[source]▶

>>45723858 #

Maybe the author would be in a better place to do that, having the expertise already. Also, as a user I'm quite happy with jq already, so why expend the effort?

4. ◴[27 Oct 25 18:08 UTC] No.45724368[source]▶

>>45723690 (TP) #

5. gnarlouse ◴[27 Oct 25 19:08 UTC] No.45725041[source]▶

>>45723690 (TP) #

JSONata looks to be more general purpose with its support for variables/statements, and custom functions. I'd probably still stick with JSONata

6. aeberhart ◴[28 Oct 25 12:00 UTC] No.45731670[source]▶

>>45723690 (TP) #

We wrote an article on this: "JQ vs. JSONata: Language and Tooling Compared". https://dashjoin.medium.com/jq-vs-jsonata-language-and-tooli...

↑

Show HN: JSON Query