59
The BEST Shell You’re Not Using - Fish - YouTube
(youtube.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Aug 2025
59 points (100.0% liked)
Linux
9845 readers
338 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
It's perfect for daily interactive use, but terrible for scripting. I write almost all my scripts in
bash, the only exceptions being convenience scripts forfishitself.Same, but I don't think it was ever intended differently; I mean the word interactive is literally in the name. If you want portable scripts, use bash. For simple helpers, quickly define a function. If you feel your script becomes too long, use Python.
Agree, although I've recently replaced the python usecase with Go. Almost as easy to write, but much faster and safer.
Oh yeah, I never used Python myself and did some very simple (but IMHO too much hassle in bash) Go stuff some time ago. It's a really good language for that, and if you can't build on the target, the binary is statically linked anyways.
How is Go safer?
Well, it's statically typed, and it's memory safe. (There can be some race conditions during concurrent execution, but that's not relevant for simple scripts.)
I still work with bash scripts from fish (to interoperate with bash users), but it's more like how I use python: the interpreter is specified either in the shebang or explicitly on the cli command invoking the script. It works quite well actually