Re Go being statically linked: great! It's meant to be a language for writing services. Those are typically deployed by creating a giant tarball of all the artifacts needed to deploy a service, copying it to all the hosts that will run it, extracting in place, and restarting. In this case, the tarball is the compiled executable. You can copy it to its server and have everything required to run it in a single tidy package.
Contrast with a Java deployment where the tarball will contain many JAR files, etc. Rolling back to a previous version either involves a symlink shuffle and restart or updating CLASSPATH to point to the old version. The Go equivalent is stopping the service and running the previous binary.
Static linking would be a pain in the ass for replacing everything in