[dietr1ch]

The problem is that I forgot (if I ever knew) bash.

I can write fish, scripting or interactively on my shell without thinking too hard about the syntax, but when scripting in bash I require an example or using my snippets to be sure I'm not shooting myself on the foot or writing something that bash will reject right away.

[lillecarl]

The trick is to use "shellcheck" on your bash scripts, it's an overly anal linter that'll keep you sharp, and it's 2026, everyone can script bash with AI :)

But yeah the syntax with [[, if fi, while stmt; do; done, "$@", case esac, "${!VAR}" and others makes me long for the day fish shell gets "euo pipefail" mode so I can stop writing bash or || true :)

[chuckadams]

I think the last time that errexit and pipefail were brought up to the fish devs, we were treated instead to an essay about how errexit is a total hack in bash, how it has all kinds of places where it doesn't work as expected, how it's special-cased away for some constructs, etc. None of which is wrong, but it's still a whole lot better than the nothing that we have with fish now.

So we still have this inflection point where scripts eventually have to graduate into a "real" language, and while those languages give us proper data types and structures on one hand, they take away conveniences like pipes with the other. It's 2026, and we managed to crack artificial freakin' intelligence before we got a decently evolved shell into the mainstream. </yells-at-cloud>