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.
I’m a former (long long ago) Linux admin and a current heavy (but not really deep) powershell user.
The .net-ification of *nix just seems bonkers to me.
Does it really work that well?
It IS bonkers. As a case study, compare the process of setting up a self-hosted runner in gitlab vs github.
Gitlab does everything The Linux Way. You spin up a slim docker container based on Alpine, pass it the API key, and you're done. Nice and simple.
Github, being owned by Microsoft, does everything The Microsoft way. The documentation mentions nothing of containers, you're just meant to run the runner natively, essentially giving Microsoft and anyone else in the repo a reverse shell into your machine. Lovely. Microsoft then somehow managed to make their runner software (reminder: whose entire job consists of pulling a git repo, parsing a yaml file, and running some shell commands) depend on fucking dotnet and a bunch of other bullshit. You're meant to install it using a shitty
setup.shscript that does that stupid thing with detecting what distro you're on and calling the native package manager to install dependencies. Which of course doesn't work for shit for anyone who's not on debain or fedora because those are the only distro's they've bothered with. So you're either stuck setting up dotnet on your system, or trying to manually banish this unholy abomination into a docker container, which is gonna end up twice the size of gitlab's pre-made Alpine container thanks to needing glibc to run dotnet (and also full gnu coreutils for some fucking reason)Bloat is just microsoft's way of doing things. They see unused resources, and they want to use them. Keep microsoft out of linux.
What type of .net-ification occurs on *nix? I am current linux "admin" and there is close to 0 times where I've seen powershell not on windows. Maybe in some microsoft specific hell-scape it is more common, but it's hard to imagine that there are people that can accept a "shell" that takes 5-10 seconds to start. There are apps written in c# but they aren't all that common?
I honestly don’t know but there must some translation happening between .net objects and *nix.
And .net “core” started supporting Linux like a decade ago. I’m guessing they’re related ¯\_(ツ)_/¯
I usually only use the terminal when I don't find an alternative, but powershell usually feels a bit saner than bash.
I've also tried nushell, also nice, but in a few situations powershell despite usually being verbose was more "elegant".