What is the difference between #!/bin/bash and #!/usr/bin/env bash?

marked as duplicate by Thomas Dickey, MelBurslan, PersianGulf, Jeff Schaller, Community Mar 22 '16 at 23:28

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 1
    In my experience, programmers who are hostile to the idea of systems administration and just want a quick hack to get their code running now without any regard for the future are in favour of #!/usr/bin/env, while sysadmins who are hostile to the idea of unholy messes running out of some dev's home directory (with a custom hacked version of python or whatever) are against it because they know the dev will eventually lose interest, move on to something else, and it will become unmaintained and unmaintainable - and if it is an important system service, it will die when the dev leaves. – cas Mar 23 '16 at 23:53
  • 2
    i.e. it's the perennial conflict between sysadmins who think important code should be integrated into the system as much as possible, and programmers who just want the code they're working on right now to work so they can move on to the next task on their schedule. The Devops idea was supposed to solve this by encouraging sysadmins and developers to work more closely together, but has mostly become a means for bean-counters to say "we don't need a sysadmin, we can make a programmer do that job", even though the tasks and skill-set of both are very different - complementary, but different. – cas Mar 23 '16 at 23:56
  • @-cas Thanks for the detailed explanation that really helped me. – Programmer Mar 23 '16 at 23:59
  • guess which side of the fence i sit on :-) – cas Mar 24 '16 at 0:01
  • @-cas Personally I think you are on the sysadmin side. Could you give me your advice on this please? unix.stackexchange.com/questions/271809/… – Programmer Mar 24 '16 at 0:08

Browse other questions tagged or ask your own question.