this post was submitted on 10 Nov 2025
146 points (99.3% liked)
Linux
10098 readers
912 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What benefits does a shell like this have over bash and how hard is it to transition?
it has loads of features that would require extensions or plugins in bash, like autocomplete, abbreviations, or fancy prompts, except they all work out of the box and with minimal configuration and behave intuitively
fish is also a much nicer language to write scripts in than bash
totally painless to transition, your bash skills are all transferable
I rewrote my entire ~/.local/bin repo of scripts from bash to fish and they are probably 50% shorter on average, actually understandable after not reading them for 6 months so highly maintainable, and actually fun to write in comparison. Argument parsing is also such a breeze.
I love it. Been using it a few years now and I'll never use a Bourne style shell again, interactively. Nushell is the only other type of shell I've my eyes on, but that seems more useful if I'm in a position where I need to process a lot of data like logs or something.
At the end of the day, fish is still a language for the shell, hence not necesaarily readable if you don't pay attention to that kind of thing. The difference is that the special-character count drops by like 80% and it is actually possible to write something readable. Imo this is next to impossible in bash. Also their builtins are pure love. The
stringcommand covers pretty much anything you might ever wish to do with any kind of string.i made the transition from fish to nushell and can confirm all this stupid JSON data and YAML config was the reason
You made a full transition? Or just when you are working with the data and configs?
it started just dropping in to mess with some data. now it’s my daily driver, and i have a trove of scripts that are my docs as code for systems like systemd or stuff that is specific to work
Do you miss fish at all?
nah nushell does all that and more. i think fish is a good alt for someone who knows enough bash to know that scripting it sucks. if you want autocomplete and plugins n stuff it’s probably the most ergonomic POSIX-like shell out there.
Cool. I might experiment a bit with nushell then, I just don't have a use case for it though, that's mainly been the "blocker". I have no real motivation to switch. Maybe it's better suited for a DevOps kind of situation or similar.
If on he other hand you want a transition that's really painful and slow but sooo rewarding (highly subjective, of course) you can look into nushell. They just said "screw this 50 years of conceptual baggage and let's do it data centric and proper".
I still am at perhaps 10% the speed of my zsh setup but the concepts are so intriguing I'm sticking to it. At least I try to ...