←back to thread

Show HN: JSON Query

(jsonquerylang.org)
147 points wofo | 3 comments | 27 Oct 25 16:22 UTC | HN request time: 0.678s | source

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. memelang ◴[27 Oct 25 17:54 UTC] No.45724185[source]▶
I've been working on an ultra-token-efficient LLM-friendly query language. https://memelang.net/09/
replies(1): >>45725129 #
2. gnarlouse ◴[27 Oct 25 19:15 UTC] No.45725129[source]▶
Cool idea! Although without looking closer I can't tell if "meme" is in reference to the technical or the colloquial meaning of meme.

Admittedly I don't know that much about LLM optimization/configuration, so apologies if I'm asking dumb questions. Isn't the value of needing to copy/paste that prompt in front of your queries a huge bog on net token efficiency? Like wouldn't you need to do some hundred/thousand query translations just to break even? Maybe I don't understand what you've built.

Cool idea either way!

replies(1): >>45726059 #
3. memelang ◴[27 Oct 25 20:44 UTC] No.45726059[source]▶
Thank you. That script prompt is just for development and exploration. A production model needs to be trained/fine-tuned on Memelang first. We're working on this now. The math says we can deliver a model 1/2 the size of an equivalent model for SQL.