>>920547
Zsh is a good, extensible shell that sacrifices its last semblance of Unix respect for sheer power, which isn't bad, albeit really ironic considering its largest userbase is MacOS users who, paradoxically, also favor MacOS because it's "real BSD" and not "GNU bloat"? I'd rather not think about it for fear of confusing myself.
>>920604
Fish is a good end user shell because of its syntax coloring and man page completion. Both of those are technically things that Zsh is capable of doing when extended with plugins, but Fish still gets one up on Zsh for the simple fact that these features are distributed with the official project. Combined with its licensing, it's basically burrowed a niche as the shell for MacOS. In contrast, Zsh is still used by default in some projects, but it really illustrates Zsh's limited scope. Because Zsh has to be extended with plugins, it really doesn't make sense as the default install to a distribution. Where it does make sense is in live mediums, and that's as far as Zsh goes, really. Of course, most MacOS users find themselves reaching for another Unix shell and, between a later Bash than the one distributed on MacOS and the glamorous Zsh often reach for the latter.
But what you should really be using is Eshell. Back when I used FVWM and didn't even know how to use Emacs, I would literally launch Emacs with Eshell mode already open just because it was so powerful. Before Cygwin and the GNU Subsystem, Windows users who knew how to use Emacs would use Eshell because of it replicated most of the features and coommands from GNU CoreUtils and Bash entirely in Elisp. The Emacs core interacts directly with the kernel, so even though Eshell is technically an Emacs mode, it has as much power as a shell, plus the versatility and consummate integration of an Emacs package. Ironically, its Zsh's pursuit of extensibility that reveals how weak its plugin ecosystem really is. The fact that Zsh's plugins are limited to Zsh is the nail on the coffin. Eshell can tap into literally every minor mode in the Emacs ecosystem, which not only means an incredibly broader scope of packages but significantly more mature packages, packages so nuanced and seemingly impertinent that no one would ever think to implement their solutions in Zsh, but in Emacs we have them, and they've had years upon years to grow into fruition. In Elisp, Eshell can not only be riced easier, but it can be riced better. With text completion, even Zsh's completion, for as much better as it is than that of Bash is like child's play compared to the multiple more configurable completion paradigms with their fuzzy search and flex search than could ever be achieved with either shell.
Basically, every one should go to >>>/emacs/ and forsake this distro-posting hellhole.