Earlier quoted context omitted.
> (installing go on every machine is not solving a portability problem, it is the portability problem) but I'm going to leave that aside. What a clueless reply. Complete FUD. Yeah, you can "leave that aside" because you have no clue what you're talking about. The ONLY place Go needs to be installed is on the developer's machine. With Go you write, you compile/cross-compile and SHIP THE COMPILED BINARY job done. Do so…
I think the question assumed that you can run go in a script-language mode. Because you do want the source of shell-scripts on the local machine. So it is easy to make changes by system admins/non-developers. Scripting is for glue functionality after all…
You can also use env-vars and flags in Go.
Which many would argue leads to more robust "admin glue functionality", because the admin controls how much non-admins can mess around with instead of allowing them to mess around with the core shell-script functionality.