I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I see this sort of thing too. I see it a lot with people newer to the shell, who use zsh on a Mac (and use oh-my-zsh like people use jQuery). They run a cropper when their simple scripts have to work inside a container running a different OS. Particularly things like sed -i.
Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
It took me forever to switch from POSIX-Shell/KSH to BASH because, up until the late-aughts, BASH wasn't a standard part of the OSes I was administering at the time. Really, it wasn't until my customers and employers started to use VMware to "virtualize all the things" – and the accompanying switch from legacy UNIX solutions to Linux — that I made the switch. Even though KSH and BASH script similarly and and have a lot of overlaps in interactive functionalities, I tend to be a "power user" ...which tends to magnify those slight differences.
It used to really gripe me during that period when I'd ask junior team members "why are you using an add-on shell" and, invariably, the response was "arrow-history" or "tab-completion". I mean, there were a lot of good reasons to prefer BASH, but, at the time, those two features were pretty standard (if you knew the shell-options to enable them), so, those features didn't seem to be worth running into scenarios where you logged in to fix a system but were handicapped because the main tool in your "SA's toolbox" was missing. :p
I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
Whenever I see someone go on about how zsh is the new cool, I ask them what they like about it. Almost everything they say is either from an add-on (like oh-my-zsh) or also available in every other shell you're likely to use.
The things that are different between shells are not thing they ever do.
I'm in the habit of making every script POSIX if there's not a good reason. I'm going to be doing a workshop on command-line skills at my office soon and want to go full-on YAGNI.
Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
I see this sort of thing too. I see it a lot with people newer to the shell, who use zsh on a Mac (and use oh-my-zsh like people use jQuery). They run a cropper when their simple scripts have to work inside a container running a different OS. Particularly things like
sed -i.It took me forever to switch from POSIX-Shell/KSH to BASH because, up until the late-aughts, BASH wasn't a standard part of the OSes I was administering at the time. Really, it wasn't until my customers and employers started to use VMware to "virtualize all the things" – and the accompanying switch from legacy UNIX solutions to Linux — that I made the switch. Even though KSH and BASH script similarly and and have a lot of overlaps in interactive functionalities, I tend to be a "power user" ...which tends to magnify those slight differences.
It used to really gripe me during that period when I'd ask junior team members "why are you using an add-on shell" and, invariably, the response was "arrow-history" or "tab-completion". I mean, there were a lot of good reasons to prefer BASH, but, at the time, those two features were pretty standard (if you knew the shell-options to enable them), so, those features didn't seem to be worth running into scenarios where you logged in to fix a system but were handicapped because the main tool in your "SA's toolbox" was missing. :p
Whenever I see someone go on about how zsh is the new cool, I ask them what they like about it. Almost everything they say is either from an add-on (like oh-my-zsh) or also available in every other shell you're likely to use.
The things that are different between shells are not thing they ever do.
I'm in the habit of making every script POSIX if there's not a good reason. I'm going to be doing a workshop on command-line skills at my office soon and want to go full-on YAGNI.
Won't get any arguments from this curmudgeon (get off my lawn!).
:)