Examples could be things like specific configuration defaults or general decision-making in leadership.
What would you change?
Examples could be things like specific configuration defaults or general decision-making in leadership.
What would you change?
For Arch Linux:
I couldn’t agree more with this, projects like artix are undermined by all the hard dependencies on systemd and Bash.
Void attracted me because of the support for posix, runit and musl (plus good zfs support). It’s unfortunate that Arch doesn’t have that greater portability.
Weird way to spell fish
But why zsh? I thought it’s basically just bash?
Why not fish, oil shell or whatever is up with ddevault’s shell?
There are many advantages relative to bash, especially much better array handling, and comprehensive globbing and expansion expressions. You can reduce your reliance on external tools, which may have multiple alternative implementations (a source of unpredictability).
Some defenses are written up at
https://www.arp242.net/why-zsh.html
(not my post)
For me, fish’s differences from older shells count against it without offering any compelling benefits.
Newer shells like nushell and oils/ysh are exciting and have a lot going on, but are not mature or familiar.
I have been using s6 daily on all my machines for 6 years now, with 66 which makes it easier.
Runit is also there as backup when something experimental fails.
I don’t know whether dinit is portable in musl or xxBSD,
I don’t disagree on principle with posix, and I use zsh but on Arch it wouldn’t be arch without BASH.
The entire package manager (pacman) is written in intense bash use.
@Andy @tet