Compiling in production? so this is the lang to "go" in case you're such kind of sysadmin which allows a compiler in production.<p>And have I to assume, it's the lang to "go", in case you're the kind of sysadmin which does not package things using the platform standards?<p>Is "go" be the solution to "administer" backups, monitoring, deployment, staging, network devices, provisioning, on a heterogeneous and scalable environment ?<p>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.<p>Fact 1) Sysadmin should be polyglot. For her needed tasks, and for the apps to support.<p>Fact 2) The right tool for the job. There is many many sub-jobs to administer a system properly (including security), there is no "one tool".<p>Fact 3) The good sysadmin is invisible, and her job goes unnoticed. Even if it's not the same to support a single app in a few servers, than to administer a multinational company internal and external networks, I still think that adding "go" to any system planning, just to "administer it", is crazy.<p>Fact 4) How many good sysadmins are good in "go"? you know, people moves, teams change, requirements change... is this choice really "helping" on the task of "administer" the infrastructure of the company in the long term?<p>Anyway, I don't say it will not work. There are many environments, and different people. It may work. I simply think this is not a "general purpose" advise to follow.<p>Congrats if it works in the case mentioned. Anything that always just works, is great, even if not advisable for other environments, teams or companies.