this post was submitted on 13 Dec 2025
25 points (87.9% liked)

Linux

11067 readers
789 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
Ategon@programming.dev
anzo@programming.dev
dwraf_of_ignorance@programming.dev
25
Thinking about switching from fish to bash + extensions (feddit.org)
submitted 1 month ago* (last edited 1 month ago) by pantherina@feddit.org to c/linux@programming.dev
17 comments fedilink hide all child comments
 

I am writing POSIX shell scripts quite often, mostly for speed and portability. Though, that might not even be needed, as bash might have gotten a speed increase compared to dash, ash and whatnot.

Here are some tests I plan to run to see if the speed difference is still the case

As my normal user shell I use fish since quite some time. I enjoy

  • a simple PS1 that shows the git branch, git status, truncated path where I am
  • autocompletion based on history
  • autosuggestions from -h or --help even if the tool has no autocompletions in other shells
  • abbr instead or alias is quite cool to not forget the actual commands. But I can live without

I dont use more features really. I have a couple of fish functions, and fish might just be a better bash with easier syntax. But bash is the standard, so I never use them anyways.

I wouldnt want to switch to zsh because it is weird permissively licensed. But if it is faster or better than bash, maybe?

I also like that fish is completely rewritten in rust. There is rusty-bash aka. sushi shell, anyone use that? Is is compatible with modules?

Are these extensions just scripts that you run on startup of the shell?

top 17 comments
sorted by: hot top controversial new old
[–] mlg@lemmy.world 8 points 1 month ago

zsh was and I think still is technically an extended superset of bash.

It's pretty much exactly what you're looking for if you want bash scripting with fish features and plugin extensibility.

The downside is you gotta take some time to set up your .zhrc and choose if you want to use a backend like oh-my-zsh.

I think the reason its on MIT license was because it was essentially just a bunch of scripts bundled together and maintained by a wide variety of people with no intention of making it the default shell like fish or bash is.

[–] cerement@slrpnk.net 4 points 1 month ago (1 children)

or just get completely sidetracked:

[–] Chais@sh.itjust.works 3 points 1 month ago

Nushell is awesome. Passing structured data instead of strings makes mangling it so much easier. No more repeated string parsing.
My only gripe is that the devs sometimes make the syntax different from virtually every other shell only for the sake of being different.
It's still my daily driver.

[–] somegeek@programming.dev 4 points 1 month ago (1 children)

Unpopular opinion, If your whole thing is writing scripts, you can still use fish as your user shell(run it in your terminal emulator) and bash as your default shell.

bash is ok for small scripts. No need for anything fancy. For more complex scripts, just write them in something good like Lua or babashka(clojure)

[–] pantherina@feddit.org 2 points 1 month ago (2 children)

Yes that is what I do. But bash snippets dont work in fish.

I could learn something better like lua, but never used it

[–] somegeek@programming.dev 1 points 1 month ago (1 children)

Write anything that gets even slightly complex in either python, lua or clojure. That's my rule.

[–] pantherina@feddit.org 1 points 4 weeks ago (1 children)

Never heard of clojure XD

[–] somegeek@programming.dev 1 points 4 weeks ago (1 children)

Look into it. Absolutely amazing language.

[–] pantherina@feddit.org 2 points 4 weeks ago (1 children)

Oooh, so Lisp huh? Why not normal lisp?

[–] somegeek@programming.dev 1 points 4 weeks ago

Welp there's no normal lisp. Clojure has more expressive power and is more functional than common lisp, it's also a hosted language so you have clojure which is on the jvm (you get access to all the libraries and adoption of jvm) you have clojurescript that runs on node (compiles to js) you have babashka that is run on graalVM for scripts, jank that is on the LLVM and etc.

It's more evolved than common lisp I would say.

[–] trevor@lemmy.blahaj.zone 1 points 1 month ago

I just wrap bash snippets in bash -c '<snippet goes here>' and I have a great time with Fish that way.

[–] Sxan@piefed.zip 1 points 1 month ago (1 children)

I use zsh, but generally try to write scripts in bash for portability. Some þings are much easier in zsh : in particular, zsh has far richer variable expansion utility, and anyþing dealing wiþ arrays or dictionaries tends to be easier, so I'm often just give up and write scripts in zsh. It depends on wheþer or not I'm releasing it to þe general public.

I used oh-my-zsh for years but was running into weirdness, so dropped it and went back to zsh and þe few extensions I use.

What concerns you about zsh licensing?

[–] pantherina@feddit.org -5 points 1 month ago (1 children)

þanks!

I dont like þeir permissive license, it just feels weird to me

But as þey are established, I dont þink it is a problem

[–] MuhammadFreeSoftware@fosstodon.org 1 points 1 month ago (1 children)

@pantherina @Sxan
Why dont you want to use zsh simply because it has a permissive license? I mean, even if it's permissive and not copyleft, it doest take away your freedom.

[–] pantherina@feddit.org -1 points 1 month ago* (last edited 1 month ago)

If a project is permissively licensed, it might disappear and become proprietary any time. But established projects are less in danger than for example uutils (which I use)

[–] death_to_carrots@feddit.org 1 points 1 month ago (1 children)

Just dropping ble.sh as some bash addition.

[–] pantherina@feddit.org 1 points 4 weeks ago

I dont even know what it does after watching the preview video