At the time of v0.1.0, the author deemed it most appropriate to use the original jq.

However, managing C-related stuff during build time had to be undertaken, and this was underestimated at the release of v0.1.0. After actually releasing and taking a look the installation error issues that were raised, it became apparent that continuing to use jq might not be the best decision.

Then, there is a project in Rust called jaq, which is a jq-clone. I hope to discuss whether or not to replace jq with jaq, and whether it is feasible to do so.

Here's a rough outline of the pros and cons:

jq (j9)

• pros
  • As an original implementation, all filters defined here are, of course, available for use
• cons
  • Requires management of C dependencies, which might pose issues during build phase
    • error: failed to run custom build command for j9-sys v0.1.2 #6
    • Not running by default on AlmaLinux 8 #13
    • Install not working #1

jaq

• pros
  • pure Rust, there is no need to manage C dependencies
• cons
  • jq-clone, not all filters may be supported
    • e.g. New filters in jq 1.7 01mf02/jaq#112
    • My concern is with this point. Ideally, it would be better if all features were available for use (Or maybe it's sufficient if only the basic filters are available...?)