libxo VS fx

> In FreeBSD, this problem was solved with libxo[0]:

Libxo happens to be in the base system, but it is generally available:

* https://github.com/Juniper/libxo

* https://libxo.readthedocs.io/en/latest/

Or make it flexible:

> libxo - A Library for Generating Text, XML, JSON, and HTML Output

* https://github.com/Juniper/libxo/

* https://wiki.freebsd.org/LibXo

Want structure? Ask for JSON or XML and parse. Otherwise it's the regular text output.

Can you trust it? Cli tool output is not exactly stable. I thought that's why libxo exists?

https://github.com/Juniper/libxo

Please consider https://github.com/Juniper/libxo or something even better than that.

That would look a lot like FreeBSD. Many of the FreeBSD userland tools are set up to use the excellent libxo (https://github.com/Juniper/libxo) to allow the user's choice of how things are output.

Fx improves this with an interactive JSON processor made for developers. It combines viewing capabilities with powerful transformation functions that make complex data manipulation simple.

Any viewer of data that has 50,000 elements in it has this many items with a scroll wheel. It doesn't matter if it's on the screen at the same time, this is the kind of thing that the UI is supposed to be abstracting away from you; you just describe the UI and the renderer makes it appear on the screen. Example apps (not built with Ink, just some that fit into this category): less, https://fx.wtf, sqlite...

And this is why React apps end up with bad performance by default. Doesn't crop up in simple tests and light usage, but the bad scaling will catch up with you when you deploy to production.

Coincidentally, yesterday I decided I needed a JSON TUI and landed on fx (https://github.com/antonmedv/fx), which seems to have come out of the Wave terminal project and looks quite similar to jless. Also uses vim keybindings.

Seems like a pretty good collection of a lot of the tools I hear about these days, and also use myself sometimes.

I also like `fx`, which is like a combination of `jq` and `gdu`.

https://fx.wtf/

Oh, and also `gdu`, which is like `ndu` but faster:

https://github.com/dundee/gdu

This is great, I could see myself using it daily. The only hindrance I've found so far is navigating large responses. Would be cool to have some way to collapse chunks of JSON (a la https://github.com/antonmedv/fx), or even just more vim key navigation, like G/gg, %, {/}, and search.