@nixCraft Because I have decades of ingrained programming habits tied to Bash? Mind you, I also already have to remember programming quirks for Busybox Ash, and Jenkins Dash. :-(
Zsh is interesting, were I coming in "cold", or doing another forced pivot like I did from Csh back 25 years ago… I'd likely adopt it.
@nixCraft ZSH has compatibility mode with sh, but it disabled by default, you can enable it with:
emulate shAlso, I'm using ZSH btw
@nixCraft Because it is not the standard across the zillion of servers i manage.
It is a good alternative if you work mainly in one host or in a few.

@nixCraft Because I simply do not need to.
The few features zsh/fish offer over bash are not enough for me to switch.
- zsh (with oh-my) as the interactive shell on my own boxes
- bash for scripting to be portable
- whatever I find on the other boxes I work on, mainly ash and bash
@nixCraft wait, no subshells in fish?
fish people, do you ever miss it / feel the need for it?
@nixCraft
I tried out fish and rejected it. For scripts, note line 1 of the table. For interactive sessions, what i remember offhand:
a) tab completion on options wipes out half the screen when invoked. Hey I was *using* my history before fish got in the way. It weighs against the nice benefit of extracting argument hints from the man pages.
b) tab completion defaults to files instead of options.
c) the colour coding mechanism might have potential, but DEFAULTS MATTER. Dark blue on black???
@nixCraft I use Zsh, for its simplicity, diverse plugin ecosystem and bash compatibility.
I don’t use any frameworks like ohmyzsh or zap whereas I have configured it to a point where my profile is my own framework which is perfectly fine for my usage.
With that said I really wish bash has features similar to Zsh and I could switch back to bash at one point in future.
@nixCraft 1. Litteracy among coworkers: most of the group knows some level of bash, so that settles it for scripts.
2. Right tool for the job: the moment I need syntax highlighting or floats, is the moment I will need to shift to a more advanced env anyway, so the extra features of zsh and fish aren't that attractive. bash's native regex support is probably as far as I'll go before switch to Perl/Python/etc.
But that is obviously dependent on one's typical usecase.
@nixCraft does sh respond to the 'history' command?
(As it does in, say, tcsh in FreeBSD.)