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 some homework next time before engaging in completely unfounded FUD.
Literally five seconds on Google could have shown the guy he was completely wrong.
But no, instead he posts unfounded FUD about how he will courteously "leave aside" the demonstrably INCORRECT claim that Go runtime needs to be installed on all machines that a Go program runs on.
So don't give me a hard time about it when it was that poster who made the original arrogant comment.
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.
in corporate environments, it is not easy to (nor should it be) to require every desk to install Go. If you are hired to script something (and scripts are even more important in corporate environments) and require a new piece of software to be installed, and a new language for staff to maintain, it's imposing a great burden and could very well be rejected.
I don't not know what I'm talking about, and I'm not trying to FUD, I'm trying to suggest "gird your loins". But also, I said that was not the point of my comment, I just didn't want you to think that through my silence I had accepted your earlier suggestion.