3 ms·

I would also be interested in some more detail on this bullet: - *qq* is not a full *jq/\*q* replacement and comes with idiosyncrasies from the underlying go

• kitd 2y ago
  From [1], there are a few differences that arise from gojq ignoring object key sort order (which you shouldn't really rely on anyway). [1] https://github.com/itchyny/gojq#difference-to-jq https://github.com/itchyny/gojq#difference-to-jq
  • arandomhuman 2y ago
    That’s it pretty much the only thing of note I’ve encountered. But yes I just mean it may not be a perfect drop in replace in all existing scripts at this time for jq like tools for other formats since they will likely take a lot of care in having the encoder for their designated format working well. qq still has a few bugs to iron out and more testing to do.
• wwader 2y ago
  Note that gojq also fixes and improves on some things compared to jq, like arbitrary-precision arithmetic (jq only preserves), some semantic and parsing improvement and fixes that will likely happen in jq at some point also, time zone/formatting/parsing fixes, etc