| ▲ | jenders 2 days ago | |
As a seasoned shell programmer, when I see set -euo pipefail, I know immediately that low quality code “batched list of commands”-type code follows. It’s bad code smell and an anti-pattern as far as I’m concerned. Anyone who has actually has taken the time to learn POSIX/BASH shell to any degree or complexity knows that it’s fully capable of catching errors in-band and that a .sh file isn’t just a dumping ground for repeating your shell history. | ||
| ▲ | naruhodo 2 days ago | parent | next [-] | |
For anyone looking for supporting evidence: https://www.reddit.com/r/commandline/comments/g1vsxk/the_fir... "set -euo pipefail" comes with footguns. | ||
| ▲ | matheusmoreira 2 days ago | parent | prev [-] | |
> a .sh file isn’t just a dumping ground for repeating your shell history Maybe it should be? As fun as it can be to write complex software in these legacy Turing tarpits, results aren't that great no matter how hard we try. Makefiles are another example. | ||