Explanation for newbies:
-
Shell is the programming language that you use when you open a terminal on linux or mac os. Well, actually "shell" is a family of languages with many different implementations (bash, dash, ash, zsh, ksh, fish, ....)
-
Writing programs in shell (called "shell scripts") is a harrowing experience because the language is optimized for interactive use at a terminal, not writing extensive applications
-
The two lines in the meme change the shell's behavior to be slightly less headache-inducing for the programmer:
set -euo pipefailis the short form of the following three commands:set -e: exit on the first command that fails, rather than plowing through ignoring all errorsset -u: treat references to undefined variables as errorsset -o pipefail: If a command piped into another command fails, treat that as an error
export LC_ALL=Ctells other programs to not do weird things depending on locale. For example, it forcesseqto output numbers with a period as the decimal separator, even on systems where coma is the default decimal separator (russian, dutch, etc.).
-
The title text references "posix", which is a document that standardizes, among other things, what features a shell must have. Posix does not require a shell to implement
pipefail, so if you want your script to run on as many different platforms as possible, then you cannot use that feature.
What else are you going to do, though?
If you have some particular and complicated task then sure you'd probably write a program for it in a specific high-level language. But that isn't what the shell is for.
If you've already got a bunch of apps and utilities and want to orchestrate them together to do a task, that's a good shell use case.
Or if you have a system that needs setup and install tasks doing on it to prepare for running your actual workload, that's also a task which the shell is ideally suited to.
Shell scripting always has a place, and I can't see it being made obsolete any time soon.
People keep on telling me that python is a "scripting language" but honestly I would rather use the shoddiest and most barebones shell you would give me than python if I had to make a script. It all boils to interfaces, and there are more programs, libraries, and daemons that have a shell interface as opposed to whatever other "better" language there is out there. Trying to write scripts with Python or ruby or whatever will just boils down to plumbing data between external programs in a less succinct syntax. What good is type safety, try/catch, and classes if all the tools that you're using are taking in and spitting out raw text anyway?