2 ms·
> The only time this complaint is valid I've dealt with bash scripts running in high load production systems and I'm very happy I don't have to any more. Ther
by xnickb 2y ago
> The only time this complaint is valid
I've dealt with bash scripts running in high load production systems and I'm very happy I don't have to any more.
There is a reason my comment was a response and not a standalone statement. The OP was explicitly speaking about using it a professional setting.
- deaddodo 2y ago> The OP was explicitly speaking about using it a professional setting. Note the little asterisk at the end there? I've worked as a systems administrator/engineer and a DevOps Engineer at quite a few companies. Very few of them cared what shell your personal account used (and usually had zsh, if not also fish). And they wouldn't run shell scripts in production; but if they did allow that, they probably wouldn't care which one you included in your shebang (as long as the package was in our standard deploy set). Obviously that doesn't represent all places, thus why I added the caveat. However, the number of places that A) allow you to run shell scripts in production and B) are also so overly paranoid as to limit user account shell interface are probably the exception, not the rule.