rcl VS gojq

If you have to deal with tools that need to be configured with yaml, give https://rcl-lang.org/ a try! It can be "coded" to avoid duplication, with real variables, functions, and loops. It can show you the result that it evaluates to. It can do debug tracing, and it has a built-in build command to generate files like GitHub Actions workflows from an RCL file.

Cue and RCL are both json supersets, though in very different ways. Cue is based on graph unification, while RCL is a more traditional functional language. Both are typed, though the type systems are very different. Like RCL, Cue can be used to query json documents, but in RCL this is a first-class feature with similar ergonomics to jq.

Jsonnet is quite similar to RCL: both are json supersets that add variables and functions in similar ways. Jsonnet is dynamically typed, while RCL features an optional gradual type system. Where Jsonnet draws inspiration from Go, RCL draws inspiration from Python and Rust.

Like Nickel, RCL is a gradually typed functional configuration language. Where Nickel has Haskell-like syntax, RCL has C/Rust/Javascript-like syntax with inspiration from Python.

RCL can query json documents on the command line, with a more intuitive language than jq. See https://rcl-lang.org/#intuitive-json-queries and https://docs.ruuda.nl/rcl/rcl_query/.

I'm working on adding floats to the RCL configuration language (https://rcl-lang.org/) to finally deliver on the json superset promise. Blog post coming soon!

If you're looking for a human-friendly json superset (comments, non-quoted keys) that can also abstract away repetitive configuration with variables and list comprehensions, check out https://rcl-lang.org/.

This has been a good driver for me to add features to https://rcl-lang.org/. I just added List.sort for today’s problem.

Relevant: https://github.com/itchyny/gojq#:~:text=supports%20reading%2...

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

Yeap i've talked to itchyny quite a lot about various changes https://github.com/itchyny/gojq/issues/153 and also upstreamed quite a lot https://github.com/itchyny/gojq/issues?q=author%3Awader like custom iterators (to allow eval, own iterators and "empty" functions), query marshalling (query rewrite tricks) and a bunch of small things and bug fixes. But the largest change to add a JQValue interface is quite complex, other changes like extended literals is also a bit tricky.

Hmm weird list of changes for https://github.com/wader/gojq/compare/fq...itchyny:gojq:main but i guess it is because i haven't kept my main branch in sync. The fq branch should be based on latest gojq/main as of now. I usually try to rebase as quick as possible.

Let me know if you have any other questions or want to help out! maybe email etc as i usually don't check HN comments replies that often :)

gojq has support for yaml input (via a very annoying argument name) and also has the golang property of "curl binary; chmod; profit": https://github.com/itchyny/gojq#difference-to-jq

It's error reporting is also clang-vs-gcc level wizardry, and I often use it to get a helpful message instead of "ENOWORKY" from jq (I haven't tried 1.7 yet, so it could be better for all I know)

Some competition for https://github.com/itchyny/gojq. I had read somewhere that it was faster than jq - no idea if that's still the case.

JQ has a go implementation usable as a library I see. The project looks fairly active https://github.com/itchyny/gojq

I've been getting a lot of mileage out of https://github.com/itchyny/gojq#readme recently due to two things: its vastly superior error messages and the (regrettably verbose) `--yaml-input` option

I also have https://github.com/01mf02/jaq#readme installed but just haven't needed it

I use gojq with --yaml-input or --yaml-output and flip back and forth between JSON and YAML promiscuously and have 100% jq UI compat, which helps because I use jq a lot. First thing I looked at on yq is '-s', which is 'slurp' for jq. Slightly altered semantics would just trip me up, and it seems like you can make a nearly straight bijection between YAML and jq so you can just do exactly the same things with either one (with some minor exceptions.)

https://github.com/itchyny/gojq