kilo VS exa

Most of that is probably attributable to being based on Kilo: https://github.com/antirez/kilo (kinda strange they didn't link directly in their readme) - a tiny text editor written by antirez who notably also created Redis. Antirez has a bunch of really interesting side projects if you dig into their github repo.

Yeah, "micro" for an editor would be 11 kilo bytes. I bet it's possible to do a half-decent editor in C in 11KB. Antirez's "kilo" (~1000 lines of C) is 36KB when compiled with standard gcc (https://github.com/antirez/kilo).

That said, for many server-type use cases these days, 11MB isn't a huge deal. Still, I wonder if micro could be compiled on / ported to TinyGo and end up a few hundred KB? It looks like TinyGo can produce some pretty small binaries: https://tinygo.org/docs/guides/optimizing-binaries/

Anyone interested in the machinations of all of this terminal stuff should look at antirez’ kilo, a terminal text editor in under 1000 lines of code: https://github.com/antirez/kilo

There is a nice tutorial that walks through how one might write it from scratch: https://viewsourcecode.org/snaptoken/kilo/

kilo 1k of C

I always wondered how people get stuff animated on the terminal but I never had the time to look into it up until a few years ago when someone on the internet released an awesome guide on how to create a text editor in less than 1000 lines of C. What caught my attention about this was that it was based on Antirez' kilo - which is a terminal based editor.

You could start by looking at something super simple like Kilo:

https://github.com/antirez/kilo

Even I could understand this one pretty well and that's no small matter.

I just started learning Rust 2 weeks ago, and I wanted to apply my learning towards a project.Ginkgo is a small text editor built entirely in Rust. It takes inspiration from the famous tiny C-based text editor, Kilo. It also includes many Vim inspired keybindings and features such as normal/insert modes. For convenience, it also has added mouse cursor support!

Write your own editor. As an example: kilo

It depends on the scale of the project but man, if you can't build a simple CRUD app in your preferred stack and deploy it in some fashion (even if it's just a binary posted on some website, kinda like Exa) then that's just disappointing...

Can compile to a single binary to build tools like exa

Try https://github.com/ogham/exa and exa -T -L2 command . It will generate a good folder structure tree to update the question

Some of us don't want all of GNU's utilities; just on an as-needed basis. They're not as needed as they once were.

Many of these utilities have been rewritten in Rust and have more modern features.

For example, instead of ls, I use exa [1]. Or ripgrep [2] instead of grep.

[1]: https://github.com/ogham/exa

[2]: https://github.com/BurntSushi/ripgrep

fish: A very fast shell with various customization options to streamline daily commands. I discovered it through this post by @caarlos0, where he provides more details about performance and the differences between fish and zsh. Additionally, I use some CLI utilities like delta, exa, and ripgrep. Here's my dotfiles for fish.

Hi! I use this: https://the.exa.website, and the package to this: https://archlinux.org/packages/extra/x86_64/exa/

I still use exa for listing files in the terminal. It's a modern replacement for ls with a lot of useful features. With icons, colors, and git integration, it makes listing files much nicer.