Live data from Hacker News

Jaq – A jq clone focused on correctness, speed, and simplicity

github.com

191–200 of 254 posts

Re: Jaq – A jq clone focused on correctness, speed, and simplicity

#191

Earlier quoted context omitted.

I’d say the amount of time before that sneak edit from Jacques to Jack lends credibility my claim of the two’s “essential interchangability”.

You're implying I subconsciously view them the same and pronounce them the same. But I don't. Maybe your dialect of English is different than mine, but I am not you. And it was there for a while because I use Hacker News on my phone and don't check it all the time. My original sentence repeated the same word twice as a typo. It was this: > I was confused reading people say that Jacques is pronounced the same as Jacqu…

The implication I'm positing is "if you mix up words without notice, they are conceptually interchangeable". You can't disprove it by stating that words you didn't mix up without notice aren't interchangeable.

Re: Jaq – A jq clone focused on correctness, speed, and simplicity

#193

I switched to jless and never looked back. The user interface is miles ahead of everything else

It's not the same. The jq is not just a viewer. It's a JSON query lang processor.

You are correct, the user interface of jq is not the same as the user interface of jless.

Re: Jaq – A jq clone focused on correctness, speed, and simplicity

#194
post #99

Earlier quoted context omitted.

Nice find. I think I'll try it out. Although I was hoping for a real SQL type experience. I don't understand why no one just copies SQL so I can write a query like "SELECT * FROM $json WHERE x>1". Everyone seems to want to invent their own new esoteric symbolic query language as if everything they do is a game of code golf. I really wish everyone would move away from this old Unix mentality of extremely concise, yet…

Be the change you want to see. I personally don't understand why people aren't willing to learn instead. It's not hard to sit down and pick up a new skill and it's good to step out of one's comfort zone. I personally hate Powershell syntax, brevity is the soul of wit and PS could learn a thing or two from bash and "the linux way". We seem obsessed with molding the machine to our individual preferences. Perhaps we sho…

The machine is uncomplicated and simple? That is the last way I would describe modern CPUs and their peripherals.

The whole point of programming is to bend the machine towards humans, not the other way around.

Re: Jaq – A jq clone focused on correctness, speed, and simplicity

#195
post #99

Earlier quoted context omitted.

Nice find. I think I'll try it out. Although I was hoping for a real SQL type experience. I don't understand why no one just copies SQL so I can write a query like "SELECT * FROM $json WHERE x>1". Everyone seems to want to invent their own new esoteric symbolic query language as if everything they do is a game of code golf. I really wish everyone would move away from this old Unix mentality of extremely concise, yet…

While i agree about the general sentiment on preferring well defined and explicit standard as opposed to "cute" custom made languages. In this case i am not convince that SQL would be the best candidate for querying nested structures like JSON.Something like xpath maybe.

JSONPath?

https://datatracker.ietf.org/doc/id/draft-goessner-dispatch-...

Re: Jaq – A jq clone focused on correctness, speed, and simplicity

#196

> nan > nan is false, while nan If this wrong behavior from jq, or some artifact consistent with how the floating point spec is defined, surprising, but faithful to IEEE 754 nonetheless?

I used Bard after trying unsuccessfully to decipher the wikipedia page and Bard says, according to IEEE 754, nan nan should return false (0)

I wish there was some version of Wikipedia for people who speak good English (not Simple English), but aren't assumed to already be experts on the topic. Technical articles are pretty much impenetrable.

Re: Jaq – A jq clone focused on correctness, speed, and simplicity

#197

Earlier quoted context omitted.

In my case, my memory doesn't work that way. I have learnt jq several times but I don't use it frequently enough to retain the knowledge. A better tool for me would be something that uses JS syntax but with some syntactic sugar and a great man page.

What is "JS syntax"? And can you write a frontend for jq that converts "JS syntax" to jq syntax? And is the jq man page poor? I'm sure they will accept patches for it.

The jq man page is pretty good IMO. It’s where/how I learned to use jq
Post reply on HN