> you can easily write a shell script that appears to perform well enough in your test environment but has clear problems when run for real in environments with

> you can easily write a shell script that appears to perform well enough in your test environment but has clear problems when run for real in environments with significantly more items This is far from unique to shell scripts. To many times I get sent "nasty SQL" optimisation problems with the phrase "works fine in test?" or "it is really fast on my local dev environment" as part of the description. While some common constructs (loops that spawn many processes per iteration) that can make shell scripts particularly prone to this, you can't blame the language for people just not nothing to test at, or even think about, production scale.