Live data from Hacker News

Zq: An easier and faster alternative to jq

brimdata.io

121–130 of 237 posts

Re: Zq: An easier and faster alternative to jq

#121
post #86
post #74

Earlier quoted context omitted.

Sadly very few authors seem to acknowledge or even know that github wiki pages are not indexed by search engines so if it wasn't for third-party sites like github-wiki-see.page (which could stop working at any time) their contents would be undiscoverable by the very same people they are usually intended...

What? That's crazy! Does Github block indexing?

https://github.com/robots.txt

I don't see anything here about wiki specifically but maybe one of the rules hits wiki pages?

Re: Zq: An easier and faster alternative to jq

#122

Earlier quoted context omitted.

It really is a fundamental problem where lots of these important projects aren't maintained simply because the reality is the maintainers can't beat the economics of a lot of rich freeloaders having no real short term incentive to compensate these maintainers..

It’s not though, because in this case the (ex-)maintainer works at a Wall St firm.

This is exactly my point. Will he quit the paying job to work for free? How long could he maintain this for free with no other job, or with a job and additional free hours without running out of money or burning out?

Re: Zq: An easier and faster alternative to jq

#124

The name of its corporate progenitor may leave a bad taste in some mouths, but I highly recommend PowerShell for this sort of thing. It's cross platform, MIT licensed, and comes with excellent JSON parsing and querying capabilities. Reading, parsing, and querying JSON to return all red cars: Get-Content cars.json | ConvertFrom-Json | ? { $_.color -eq 'red' } The beauty of this is that the query syntax applies not jus…

Powershell's object pipes are more inspectable than any of Bourne's text-based decendants. But the tool itself occupies a niche between "write shell, dealing with esoteria of grep/sed/awk/jq/etc" and "write python getting constructs than handle complexity better than pipes".

Looking at the popularity of VSCode, I don't think Microsoft hatred blocks its adoption.

Re: Zq: An easier and faster alternative to jq

#125
post #63

Why all the hate HN? I feel the author makes his case clearly, then presents an alternative. Underneath all this is a ton of work, for which I applaud OP. It may not scratch your particular itch, but come on! Being an ass on HN is a choice. It happens far too often, and I wish everyone would just dial it back.

I don't see hate for the project here. I see criticism for the way they're trying to position it as easier than jq when it's just different than jq. It looks like a cool project on its own and doesn't need to describe jq as confusing to make that point.

But it is easier, for them.

Easier, as a universal claim, is hard to establish - you'd need to do user studies. Easier in the author's opinion is normal usage, and their opinion is as good as anyone else's. They gave a reasonable justification.

I kind of think you'd need to use both tools to have an informed opinion about which you think is easier. But most of us aren't going to do that, which is fine.

I think having strong opinions about which is easier without trying them both is weird, though.

Re: Zq: An easier and faster alternative to jq

#126

Earlier quoted context omitted.

It really is a fundamental problem where lots of these important projects aren't maintained simply because the reality is the maintainers can't beat the economics of a lot of rich freeloaders having no real short term incentive to compensate these maintainers..

> can't beat the economics This makes it sound like this is some antagonistic relationship where the OSS maintainer loses. But the idealistic scenario that you are alluding to[1] is about a developer who develops free OSS in their free time. And then, yes, very few end up paying or donating anything. But how is a predictable chain of events a loss ? What is the “economics” of it? [1] Some OSS developers do it as thei…

This is unrelated to the argument but using references that aren't references made that really confusing to read.

In any case, what I meant by the "economics" of it is that in general a person can only afford to work for free for so long before they need to pay bills, eat, have and/or acquire a standard of living that isn't poverty. If they have a day job where they are writing this software in their free time, how long can they do this before burning out?

Re: Zq: An easier and faster alternative to jq

#127
I'm sure I'm not the only person that got fed up with occasionally needing to do something more advanced and just finding the JQ incantations inscrutable.

Also prob not the first to create a project for personal use that just wraps evals in another language haha: https://www.npmjs.com/package/jsling

Re: Zq: An easier and faster alternative to jq

#129

The name of its corporate progenitor may leave a bad taste in some mouths, but I highly recommend PowerShell for this sort of thing. It's cross platform, MIT licensed, and comes with excellent JSON parsing and querying capabilities. Reading, parsing, and querying JSON to return all red cars: Get-Content cars.json | ConvertFrom-Json | ? { $_.color -eq 'red' } The beauty of this is that the query syntax applies not jus…

jq can not only process JSON input but also emit JSON output. So on that note, has ConvertTo-Json stopped mangling your JSON yet? https://news.ycombinator.com/item?id=25500632

Re: Zq: An easier and faster alternative to jq

#130
post #86
post #74

Earlier quoted context omitted.

Sadly very few authors seem to acknowledge or even know that github wiki pages are not indexed by search engines so if it wasn't for third-party sites like github-wiki-see.page (which could stop working at any time) their contents would be undiscoverable by the very same people they are usually intended...

What? That's crazy! Does Github block indexing?

There's more details on https://github-wiki-see.page/ and https://github.com/github/feedback/discussions/4992#discussi...

> we have also introduced an x-robots-tag: none in the http response header of Wiki pages

> Abusive behavior in Wikis had a negative impact on our search engine ranking

> GitHub is currently permitting a select criteria of GitHub Wikis to be indexed

Post reply on HN