bat VS jq

I'm quite new to Rust, and have been trying to learn more by working on some real solution I could see myself benefitting from, which happens to be a CLI tool at this time. I know there are some great tools written in Rust which I use day to day (such as Starship, bat, exa, etc.), but I wanted to hear experts' suggestions / recommendations on any project I should check out for clean, clear, and extensible structure (or lack thereof), and any dependencies I should start with / avoid.

I think you’re conflating different projects.

There are projects that aim for a better user experience, with better command line interface, defaults, performance and UI. These are of course breaking changes and the programs can’t be used as drop in replacement. Some examples are

- ls => exa (https://github.com/ogham/exa)

- grep => ripgrep (https://github.com/BurntSushi/ripgrep)

- cat => bat (https://github.com/sharkdp/bat)

- tree => broot (https://github.com/Canop/broot)

The person you’re replying to was speaking of a different project - uutils (https://github.com/uutils/coreutils). These are drop in replacements with identical interfaces (modulo bugs).

bat - A cat clone with wings, very nice file catter

Bat looks so cool!! https://github.com/sharkdp/bat - cat with syntax highlighting in Rust.

I think they have aliased the bat util. https://github.com/sharkdp/bat

bat (batcat)

- https://github.com/sharkdp/bat (uses `less` under the hood, syntax highlighting and git diffs)

But it can be used as a bat(https://github.com/sharkdp/bat) pager.

Here's bash-notes, it's written 100% in bash and the only dependency it has is jq, it can add, edit, remove or list notes, it uses VIM or whatever editor you may like, you can specify which terminal emulator to use and what options to pass when you execute it.

To the best of my knowledge, Vim's problems with large files are usually about long lines. If your JSON file is all on one line, that's going to be a much, much bigger problem than if it's formatted on many lines. Try formatting the JSON with jq . beforehand: jq. See if there's a difference.

NB. there is also an entry in the `jq` cookbook for parsing CSVs into arrays of objects (and keeping numbers as numbers, dealing with nulls, etc) https://github.com/stedolan/jq/wiki/Cookbook#convert-a-csv-f...

the obvious missing reference is jq https://github.com/stedolan/jq

jq

The server log output is JSON. Super-recommended to run it through jq!

If they had used an .nvmrc file instead, I could run nvm use to ensure I'm using the correct node version. In order to get this same type of behavior I use a function I wrote called nvmpe that uses jq to get the node version from the value from package.json and then nvm to set my node version.

Hi! It's more like writing jq in your struct definitions and executing them with serde::Deserialize.

I would add jq to the data wrangling section https://stedolan.github.io/jq/

Being moderately competant at jq on a team that doesn't know jq is a super power.