gojq VS dot_files

Compare gojq vs dot_files and see what are their differences.

gojq

Pure Go implementation of jq (by itchyny)

dot_files

My Shell configurations (by hoshsadiq)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
gojq dot_files
31 1
3,029 10
- -
8.3 1.8
7 days ago 11 months ago
Go Shell
MIT License -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

gojq

Posts with mentions or reviews of gojq. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-08.

dot_files

Posts with mentions or reviews of dot_files. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-01.
  • Extracting Objects Recursively with Jq
    14 projects | news.ycombinator.com | 1 Aug 2021
    I tend to use jq a lot. As others have said, sometimes jq can be hard to grasp. Often it requires multiple attempts to get the correct answer. To make it a little easier for me, I've written a helper function[0] that combines it with fzf[1] to run jq as a REPL on any json. It allows to incrementally alter your DSL without having to continually call jq. This is similar to jid/jiq but a little more powerful. It includes functions to change the preview to output raw, compact (or not), and some other things.

    I didn't use jid/jiq because jid uses go-simplejson, which is nowhere near as powerful as jq, and jiq seemed very buggy when I used it and it felt like it was hacked together. Plus there was no where to change jq's arguments while running it.

    I'm sure this function can be improved on, but this has been good enough for me so far.

    Also, I run gojq[2] instead of jq. It is a drop-in replacement for jq but is written in Go, and has some improvements over jq such as bug fixes, support for yaml input, and it also provides more helpful error messages.

    [0] https://github.com/hoshsadiq/dot_files/blob/master/zshrc.d/m...

What are some alternatives?

When comparing gojq and dot_files you can also consider the following projects:

jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]

jq - Command-line JSON processor

yq - yq is a portable command-line YAML, JSON, XML, CSV, TOML and properties processor

counsel-jq - Traverse complex JSON and YAML structures with live feedback

jfq - JSONata on the command line

zed - A novel data lake based on super-structured data

jet - CLI to transform between JSON, EDN, YAML and Transit using Clojure

gron - Make JSON greppable!

gio-example - Mirror of the Gio examples repository (https://git.sr.ht/~eliasnaur/gio-example)

HackerNews - macOS HackerNews client that aims to be a Mac-assed Mac app. Written in Swift + AppKit.

jaq - A jq clone focussed on correctness, speed, and simplicity

fzf - :cherry_blossom: A command-line fuzzy finder