rb VS jq

I like using `jq` to create line-delimited JSON and then using a language I know well (Node) to process it after that point. I find `jq '.[] | select(.location=="Stockholm")'` less readable than something like `nq --filter '({location}) => location === "Stockholm"'` because I'm much more used to Node syntax.

- https://github.com/thisredone/rb is a widely used ruby version of this idea

- https://github.com/KelWill/nq#readme is something similar that I wrote for my own use

You might be interested by this little script https://github.com/thisredone/rb

That should recursively list directories, counting only the files within each, and output² jsonl that can be further mangled within the shell². You could just as easily populate an associative array for further work, or $whatever. Unlike bash, zsh has reasonable behaviour around quoting and whitespace too.

¹ https://zsh.sourceforge.io/Doc/Release/User-Contributions.ht...

² https://github.com/jpmens/jo

³ https://github.com/stedolan/jq

What I miss from jq and what is implemented but unreleased is platform independent line delimiters.

jq on Windows produces \r\n terminated lines which can be annoying when used with Cygwin / MSYS2 / WSL. The '--binary' option to not convert line delimiters is one of those pending improvements.

https://github.com/stedolan/jq/commit/0dab2b18d73e561f511801...

If you have jq installed you can use it to make the output look nicer.

It requires jq for JSON processing and GNU parallel for concurrent searches in the notebooks.

jq is your friend.

The jq command (https://stedolan.github.io/jq/) is useful pulling that information out.