shellcheck

I like Fish because I find it has sane defaults, i.e. {coloring, autosuggestions, completions} all work well out of the box with zero or little configuration. You can replicate a fish-like feeling in zsh (coloring, completions, etc), but for that you need a plugin manager, a million bajillion finicky plugins, and then configuration/performance hell [1] happens. I tried that, got bored of it, then learned to fish and never looked back at zsh. That being said, out of the interactive shell I don't like the exoticism of fish as a scripting language; I keep preferring shebanged, shellchecked [2], defensive [3] (ba)sh scripts, they're a stable and portable evil I know. Also, I'm curious what makes you feel "lack of customization in Fish": what can you customize in Zsh that you cannot in Fish? [1] https://github.com/zsh-users/zsh-autosuggestions

I agree with this. I would just add that you can get great linting / syntax checking with ShellCheck [1] [2] [1] - https://github.com/koalaman/shellcheck [2] - https://www.shellcheck.net/ ShellCheck is in many of the distro package repositories already.

ShellCheck is right insofar as compatibility is concerned. You can only rely on the shebang supporting one argument. I'd personally just ignore that warning if I were writing for MacOS specifically, but you can configure ShellCheck to ignore certain errors that you don't care about[1]. [1] https://github.com/koalaman/shellcheck/wiki/Ignore

TIL that this quick trick [1] also would have prevented this: ${STEAMROOT:?} ...where :? throws an error if the variable is unset or empty. (Still far too scary for my taste, though!) [1] https://github.com/koalaman/shellcheck/wiki/SC2115

While not an alternative, please bugfix your bash: mv "$@" ~/.Trash/ https://github.com/koalaman/shellcheck/wiki/SC2086