#techpost
I have decided that hardcoding the interpreter path at the top of a script is fine, BECAUSE
it's a convienience to calling the script like:
<script-interpreter> <script-name>
Convieniences are not where you standardize things.
This is about saying I don't like 'env' as a standard to put
at the top of shell scripts
$!/usr/bin/env <script interpreter>
echo "this is bad"
[grenade pin pulled sound]
I have decided that hardcoding the interpreter path at the top of a script is fine, BECAUSE
it's a convienience to calling the script like:
<script-interpreter> <script-name>
Convieniences are not where you standardize things.
This is about saying I don't like 'env' as a standard to put
at the top of shell scripts
$!/usr/bin/env <script interpreter>
echo "this is bad"
[grenade pin pulled sound]