bat VS glow

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.

Charm's Glow is a joy to use, a good example of having the Charm's Bubbletea usage - but from the code perspective, it's a bit difficult to navigate as many code paths are put in the same package

glow.nvim is a wrapper around the terminal tool glow. you could probably adapt it to other terminal markdown readers tho

The problem I have with AsciiDoc (AD) and Markdown (MD) is that they are too effective (in the best way)! Follow my reasoning for a moment, please...

I was reviewing a command-line MD reader today. I think it was the nth time I've looked it over. It's called glow : https://github.com/charmbracelet/glow

I always come to the same conclusion. I don't need it. I don't need to remember to use (yet) another command line program to read MD or perform a very specific (and non-vital) function.

The reason is that MD and AD are so very easy to read. They are too effective at their jobs. They aren't like HTML tags that get in the way of the text. You barely even notice MD/AD in most(?) cases. Text plus MD/AD are incredibly easy to read without a 3rd-party program "rendering" the results.

Having said that... the only time I got really excited about MD/AD was when there was a post about Textual Markdown : https://news.ycombinator.com/item?id=34028765

It wasn't that the "rendered" text looked great (it looked beautiful, btw) but I could see 'Textual Markdown' turning into a command-line, online browser just for MD text! Think about that...

I even thought about how great it would be if the GeminiSpace folks : https://en.wikipedia.org/wiki/Gemini_(protocol)?useskin=vect... : embraced MD/AsciiDOC instead of their limited markup language.

It's exciting to think of MD/AD making themselves an alternative lightweight tagging system on the web. Exciting to think about a lightweight web in general - no tracking, adware, tons of JS, etc...

Exciting to think about a bunch of browsers growing out of this (ie; you don't need billions/yr to support MD/AD browsers) - from full-blown GUIs to, well... "Textual-Markdown".

Anyway... MD/AD would be great if it grew beyond offline use. For offline use only... you really don't need rendering. Maybe it helps a bit with really long files but otherwise...

Glow

Hadn't seen/heard of that but by googling the main difference is the markdown styling using glamour. I basically wanted [glow](https://github.com/charmbracelet/glow) with rss feeds and this was the result.

If you want to continue with this project I suggest to switch to markdown instead of creating own "language", there are multiple markdown renders for Go that you can use (something like glow).

Where glow is this little gem right here: https://github.com/charmbracelet/glow