Viewing a single comment thread. View all comments

sela_mad OP t1_is4gfb0 wrote

Reply to comment by code_architect in I'm developing a new command line tool for querying and transforming JSON files , called ~Q (pronounced "unquery"). My design goal is to create a tool that is powerful yet easy to use (aim to be more intuitive for users than existing tools such as jq). Let me know your thoughts and suggestions. by sela_mad

Thank you for your thoughtful comments!

The name has gone through several changes. I started with Q!, and then changed it to not-Q (similar to NoSQL), but since !Q looks confusing, I settled with ~Q, which looks better typographically. ~Q/Unquery is the language (used both in XCiteDB and unq), and unq is the name of the command-line tool. If enough people don't like the ~Q name, I may be convinced to drop it :-)

I got another request for examples comparing unquery and jq syntax. That's definitely something I'm going to work on.

And finally, I'm in the process of revamping the XCiteDB website and replacing it with a much better website with more technical content and links.

3

riffito t1_is58q34 wrote

Minor comments regarding the name (as I can't really comment on the rest :-D)

> ~Q

I read that as: "more-or-less Q"/"almost Q"/"approximately Q", but that might be due to my math classes from 25 years ago.

~ is not particularly handy to type on non-US keyboards (using ALT+126 here on Windows, or: AltGr+4, then spacebar... and this is on a keyboard with "Ñ"). It might hinder a bit the ability to search for ~Q.

"unQ" is less ambiguous, at least for me (and my poorly self-taught "English" :-D).

8

sela_mad OP t1_isb6otr wrote

Thank you both. Following your feedback, and after additional discussions with many people, I've decided to drop the "~Q" abbreviation, and just go with "Unquery".

The documentation, and any future reference to the language, would reflect this change.

3