3 ms·
> Aside from that, q isn't feature parity with jq which is ok at this point, but jq contains a ton of functionality that query-json misses and some of the jq o
by as-j 6y ago
> Aside from that, q isn't feature parity with jq which is ok at this point, but jq contains a ton of functionality that query-json misses and some of the jq operations aren't native, are builtin with the runtime. In order to do a proper comparision all of this above would need to take into consideration.
> The report shows that q is between 2x and 5x faster than jq in all operations tested and same speed (~1.1x) with huge files (> 100M).
While faster for somethings....that's a pretty large set of caveats!
- davesnx 6y agoAdding most of the jq operations shoudn't affect performance at all, in fact If I endup implementing streaming could be even faster. I have a issue to improve performance where I can push this forward: https://github.com/davesnx/query-json/issues/7 https://github.com/davesnx/query-json/issues/7 But sure, are caveats!