Jaq – A jq clone focused on correctness, speed, and simplicity
1–10 of 254 posts
Re: Jaq – A jq clone focused on correctness, speed, and simplicity
#2[flagged]
Re: Jaq – A jq clone focused on correctness, speed, and simplicity
#3While jq is a very powerful tool, I've also been using DuckDB a lot lately.
SQL is a much more natural language if the data is somewhat tabular.
Re: Jaq – A jq clone focused on correctness, speed, and simplicity
#4[flagged]
As an outsider, getting your code merged into a popular open source project involves a political process of convincing the maintainers that your fix should be addressed, and then convincing them they should merge your code.
Writing a fork involves sitting down at your laptop and coding it out.
Re: Jaq – A jq clone focused on correctness, speed, and simplicity
#5[flagged]
As an outsider, getting your code merged into a popular open source project involves a political process of convincing the maintainers that your fix should be addressed, and then convincing them they should merge your code. Writing a fork involves sitting down at your laptop and coding it out.
Plus of course everything needs rewritten in rust /s.
Re: Jaq – A jq clone focused on correctness, speed, and simplicity
#6I applaud this project's focus on correctness and efficiency, but I'd also really like a version of `jq` that's easy to understand without having to learn a whole new syntax.
`jq` is a really powerful tool and `jaq` promises to be even more powerful. But, as a system administrator, most lot of the time that I'm dealing with json files, something that behaved more like grep would be sufficient.
Re: Jaq – A jq clone focused on correctness, speed, and simplicity
#7This language must be the spiritual successor of Perl
Re: Jaq – A jq clone focused on correctness, speed, and simplicity
#8I applaud this project's focus on correctness and efficiency, but I'd also really like a version of `jq` that's easy to understand without having to learn a whole new syntax. `jq` is a really powerful tool and `jaq` promises to be even more powerful. But, as a system administrator, most lot of the time that I'm dealing with json files, something that behaved more like grep would be sufficient.
Obligatory reference to "gron" ("make JSON greppable"), which I find to be quite useful for many common tasks:
Re: Jaq – A jq clone focused on correctness, speed, and simplicity
#9[flagged]
Re: Jaq – A jq clone focused on correctness, speed, and simplicity
#10I applaud this project's focus on correctness and efficiency, but I'd also really like a version of `jq` that's easy to understand without having to learn a whole new syntax. `jq` is a really powerful tool and `jaq` promises to be even more powerful. But, as a system administrator, most lot of the time that I'm dealing with json files, something that behaved more like grep would be sufficient.
Have you tried `gron`?
It converts your nested json into a line by line format which plays better with tools like `grep`
From the project's README:
▶ gron "https://api.github.com/repos/tomnomnom/gron/commits?per_page..." | fgrep "commit.author"
json[0].commit.author = {};
json[0].commit.author.date = "2016-07-02T10:51:21Z";
json[0].commit.author.email = "mail@tomnomnom.com";
json[0].commit.author.name = "Tom Hudson";
https://github.com/tomnomnom/gron
It was suggested to me in HN comments on an article I wrote about `jq`, and I have found myself using it a lot in my day to day workflow