A little more verbosity on the advice might have helped. I wouldn't have properly understood you were saying without @peatmoss's reply. So without the context, your original comment just seemed like knee-jerk bash-bashing.
I've encountered many scripts written by developers on Fedora that totally fail over when run on Ubuntu specifically due to using #!/bin/sh when they really required #!/bin/bash.
I specifically said "Write clean, posix-compliant shell scripts"
Do the same developers write Java code in a .cpp file and wonder why it doesn't work? Or put <?php tags in a .erb template?
Yes, you need to test to make sure that you wrote the correct things.
* https://wiki.ubuntu.com/DashAsBinSh
* https://wiki.ubuntu.com/DashAsBinSh/Spec
* https://lists.debian.org/debian-release/2007/07/msg00027.htm...
If more people used #!/usr/bin/env bash, it wouldn't be that big of a deal.
If they wrote posix compatible shell scripts it wouldn't be any big deal because they'd just work.