If you have to use the mouse to click buttons with hover effects, is it really still the terminal? Might as well just be a GUI at that point. I guess there a corner case of wanting to run this on a server you only have headless access to. Still quite impressive for what it is though.

That cat command is neat, does it play nicely with pipes?

I don't immediately see the advantages over something like jq from just reading the readme. Maybe include a definitive example of how you would do something in jq and how you would do that same thing better in unq.

I am not so keen on programs having multiple names, especially if one is unpronounceable. I would definitely lean into one of unq, unquery, or ~q. My recommendation is unq because it is short to type and already what you seem to have chosen as the name for the executable. I highly recommend dropping the ~q branding completely. In windows ~ denotes a hidden file so it might be hidden queue.

In unix (both mac and linux) ~ denotes the "home" directory /home/<user>/ leading to the idea of "home q". This could also lead to a lot of confusion when trying to run a command such as ~q -f ~/query.unq ~/mydata.json.

In arithmetic ~ can mean "about" or "close to".

And in some Logical expressions, which I think is close to the way you want it to be used, it means not. But even in that context I would still feel compelled to pronounce it not queue.

I am not sure if you are also the developer of xcitedb but if you are I would definitely recommend having a link to click for people interested in the DB from the marketing page (https://xcitedb.com/). If it is an open source database then a link to the github page, if it is a closed source database then a link to contact sales.

Also the marking page (https://xcitedb.com/) references the Q!query language. Which is maybe this ~q language? If so then I recommend unifying the branding of this as well.

That said, other then being a programmer, I am not your target audience so take everything I said with a grain of salt.