exa VS fish-shell

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.

Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.

https://github.com/fish-shell/fish-shell/releases/tag/3.7.1

https://github.com/fish-shell/fish-shell/issues/7772#issueco...

https://gitlab.archlinux.org/archlinux/packaging/packages/fi...

A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123

An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust

It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/

And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123

We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.

They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.

[1] https://github.com/fish-shell/fish-shell/pull/9512