infrastructure VS gron

Rocky Linux is a fine successor to CentOS and was created by the original founder of CentOS, Gregory Kurtzer.

https://rockylinux.org/

https://rockylinux.org/about/

If you need enterprise support RHEL tends to be a default choice.

If you cannot afford RHEL or do not need enterprise support, Rocky Linux fills the role that CentOS once did.

Also you can use Rocky Linux, it's very close! https://rockylinux.org/

Arch Linux is pretty solid on my end, gnome is a little buggy, nothing like fedora but if you're like my mother and don't want to set anything up I get it. There is Rocky linux if you want a RHEL experience and don't need the latest packages. I don't like Ubuntu but you could go that route.

If you run into anny problems ask chat gpt. https://rockylinux.org/

If If you feel more comfortable on a RHEL based distro, there a good alternatives to CentOS such as AlmaLinux or Rocky Linux.

This situation still exists and Gregory Kurtzer's RockyLinux (Greg started CentOS originally), CloudLinux's AlmaLinux, and others exist to fill the need for a freely installable RHEL clone.

https://rockylinux.org/ :

Rocky Linux is an open-source enterprise operating system designed to be 100% bug-for-bug compatible with Red Hat Enterprise Linux®. It is under intensive development by the community.

gron (https://github.com/tomnomnom/gron) to transform it and query and then invert the transformation?

It buffers all of its output statements in memory before writing to stdout:

https://github.com/tomnomnom/gron/blob/master/main.go#L204

Have you tried `gron`?

It converts your nested json into a line by line format which plays better with tools like `grep`

From the project's README:

▶ gron "https://api.github.com/repos/tomnomnom/gron/commits?per_page..." | fgrep "commit.author"

json[0].commit.author = {};

json[0].commit.author.date = "2016-07-02T10:51:21Z";

json[0].commit.author.email = "[email protected]";

json[0].commit.author.name = "Tom Hudson";

https://github.com/tomnomnom/gron

It was suggested to me in HN comments on an article I wrote about `jq`, and I have found myself using it a lot in my day to day workflow

> So all I want is a tool to go from json => line oriented and I will do the rest with the vast library of experience I already have at transformations on the command line.*

The tool for that is likely https://github.com/tomnomnom/gron

If JQ is too much, see GRON &| Miller

gron transforms JSON into discrete assignments to make it easier to grep for what you want https://github.com/tomnomnom/gron

Miller is like awk, sed, cut, join, and sort for data formats such as CSV, TSV, JSON, JSON https://github.com/johnkerl/miller

And jless [1] and gron [2].

This is the first I'm hearing of gron, but adding here for completeness sake. Meanwhile, JSON seems to be becoming a standard for CLI tools. Ideal scenario would be if every CLI tool has a --json flag or something similar, so that jc is not needed anymore.

[1] https://jless.io/

[2] https://github.com/tomnomnom/gron