> For me, the "Zen" as sysadmin, is to impose as few toolchains and dependencies external to the _app_ to support, as possible. Going to "go" for me is as say that "java" is the lang to go if you're a sysadmin.
That seems to be the main advantage of Go that the author mentions. The Go compiler builds statically linked binaries.
Once built, the single file can be copied and run on any common system, without installing the compiler/interpreter, packages or libraries onto that system.
While I like Python, running Python scripts on servers requires considerable effort for deployment. You have to ensure that the right versions of the right packages are installed (which is even more difficult when it's someone else's server). Whereas with Go "deployment" would be just a file copy.
That seems to be the main advantage of Go that the author mentions. The Go compiler builds statically linked binaries.
Once built, the single file can be copied and run on any common system, without installing the compiler/interpreter, packages or libraries onto that system.
While I like Python, running Python scripts on servers requires considerable effort for deployment. You have to ensure that the right versions of the right packages are installed (which is even more difficult when it's someone else's server). Whereas with Go "deployment" would be just a file copy.