Shellcheck is a boon to write more (by at least three orders of magnitude) reliable shell code. I wish there were a 'set -o strict' that would make bash conside

Shellcheck is a boon to write more (by at least three orders of magnitude) reliable shell code. I wish there were a 'set -o strict' that would make bash consider all shellcheck warnings into errors as well as unilaterally set -euo pipefail. That said, bash is still my go to language for many many things because at the end of the day it's insanely efficient as that koan[0] is still valid when substituting C for mostly any other language. As an anecdote I've replaced ridiculously big and slow Rakefiles and unmaintainable ad hoc ruby code with much shorter, readable and reliable shell scripts. Using the shell doesn't mean you can't drop a call to python, perl, jq or whatever, and the composability and performance can be terrific when properly wielded. [0] http://www.catb.org/esr/writings/unix-koans/ten-thousand.html http://www.catb.org/esr/writings/unix-koans/ten-thousand.htm...