Q: A faster re-implementaiton of jq written in Reason Native/OCaml
1–10 of 196 posts
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#2This looks nice, but I was a bit dismayed at "friends don't let friends curl | bash, to install this run curl | bash".
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#3This looks interesting, but could be confusing given the programming language of the same name (https://code.kx.com/q/)
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#4Is jq slow? I have only worked with datasets up to 1mb but I’ve never had a performance issue that wasn’t attributed to my error.
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#5This looks nice, but I was a bit dismayed at "friends don't let friends curl | bash, to install this run curl | bash".
That is pretty amusing. I’ve seen some bootstrap scripts that pipe the curled output to the terminal for approval before executing it. That seems like an ergonomic alternative to curl | bash. It would be at least as useful as the terms of service warnings before you install something, anyway.
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#6Is jq slow? I have only worked with datasets up to 1mb but I’ve never had a performance issue that wasn’t attributed to my error.
Yes
I often have to pluck out attributes from streams of json records (1 json object per line) - often millions/billions.
jq is almost always the bottleneck in the pipeline at 100% CPU - so much so that we often add an fgrep to the left side of the pipeline to minimize the input to jq as much as possible.
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#7Is jq slow? I have only worked with datasets up to 1mb but I’ve never had a performance issue that wasn’t attributed to my error.
jq is pretty fast in my experience. But there have been cases where I've wanted it to be faster (dealing with a 90GB JSON file).
The main weakness seems to be streaming use cases (not having the whole file in memory at once). These are supported, but the syntax is quite awkward.
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#8Are we sure it should get a single-letter 'q' binary name though? Docs seem to point that it's short for 'query-json'? Why not call it 'query-json' and let the user decide that as a shell alias or whatever. Even the ubiquitous 'ls' and 'cd' are two characters.
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#9Hm, I thought q is synonym for querying CSV files https://harelba.github.io/q/
Re: Q: A faster re-implementaiton of jq written in Reason Native/OCaml
#10Are we sure it should get a single-letter 'q' binary name though? Docs seem to point that it's short for 'query-json'? Why not call it 'query-json' and let the user decide that as a shell alias or whatever. Even the ubiquitous 'ls' and 'cd' are two characters.
or at least qj