5 ms·

Cool news. “$PKG_MGR fish && chsh -s /usr/bin/fish $USER” is pretty essential after using bash for more than a few minutes.

fbdab103 4y ago
If only I were that brave. Too many things expect bash that I do not want that potential friction. Instead, I manually switch when I launch a terminal.
- ComputerGuru 4y ago
  Pretty much everything that expects bash will have the #!/bin/bash (or better yet, #!/usr/bin/env bash) shebang in place and will continue to work.
- doublepg23 4y ago
  Along with _most_ things having shebangs in 2023 I often run scripts as “bash script.sh” and never even bother doing “./script.sh”.
- Gigachad 4y ago
  I'd have expected much fewer since macOS switched to zsh a few years ago.
  - Macha 4y ago
    zsh is basically bash compatible, especially for the level of bash features that get exercised by 95+% of scripts
  - mlindner 4y ago
    I never got the appeal of zsh. It felt just like bash with all the interesting features of zsh hidden into advanced functionality, whereas with fish lots of things "just work" out of the box without spending a bunch of time configuring it. I'd rather have really good defaults and the option for configurability rather than not great defaults and really advanced configurability.
    - arp242 4y ago
      Changing defaults is tricky for established projects with a lot of users, because the software will change underneath for existing users who upgrade which can be very jarring. On the other hand, it makes things harder for new users. zsh starts the "zsh-newuser-install" tutorial to set up a more modern zshrc as a kind of compromise. Maybe that should be a bit easier though with just a "use all modern defaults" option. And, of course, there are many templates/projects in the interwebz. zsh has many more features than bash, and implements many things better than bash. It's like comparing IE to Firefox or Chrome.
- stavros 4y ago
  I don't understand this argument. What could break? Bash will still be there for the scripts that want it.
  - Arnavion 4y ago
    Things that expect to be dot-sourced may break. Copy-pasting commands / script blocks from other people may break. But both are surmountable problems.

fbdab103 4y ago

If only I were that brave. Too many things expect bash that I do not want that potential friction. Instead, I manually switch when I launch a terminal.

ComputerGuru 4y ago
Pretty much everything that expects bash will have the #!/bin/bash (or better yet, #!/usr/bin/env bash) shebang in place and will continue to work.
doublepg23 4y ago
Along with _most_ things having shebangs in 2023 I often run scripts as “bash script.sh” and never even bother doing “./script.sh”.
Gigachad 4y ago
I'd have expected much fewer since macOS switched to zsh a few years ago.
- Macha 4y ago
  zsh is basically bash compatible, especially for the level of bash features that get exercised by 95+% of scripts
- mlindner 4y ago
  I never got the appeal of zsh. It felt just like bash with all the interesting features of zsh hidden into advanced functionality, whereas with fish lots of things "just work" out of the box without spending a bunch of time configuring it. I'd rather have really good defaults and the option for configurability rather than not great defaults and really advanced configurability.
  - arp242 4y ago
    Changing defaults is tricky for established projects with a lot of users, because the software will change underneath for existing users who upgrade which can be very jarring. On the other hand, it makes things harder for new users. zsh starts the "zsh-newuser-install" tutorial to set up a more modern zshrc as a kind of compromise. Maybe that should be a bit easier though with just a "use all modern defaults" option. And, of course, there are many templates/projects in the interwebz. zsh has many more features than bash, and implements many things better than bash. It's like comparing IE to Firefox or Chrome.
stavros 4y ago
I don't understand this argument. What could break? Bash will still be there for the scripts that want it.
- Arnavion 4y ago
  Things that expect to be dot-sourced may break. Copy-pasting commands / script blocks from other people may break. But both are surmountable problems.