Edit: As others pointed out, Go is compiled binary and does not required runtime (like JVM) so versionning is not issue. Thanks for clearing up.
So if you have multiple different Go applications on one server, and they use some of the same libraries, then each application's binary will contain a copy of that library.
It makes things a little redundant, but also simplifies the deployment process.
edit: The only exception is if you are using cgo and liking to existing C libraries. In pure Go there is no linking.
By the way, you can actually do the same for Python using cx_Freeze; it'll create a single executable with Python + libraries + you code.
[1] http://cx-freeze.readthedocs.org/en/latest/script.html#scrip...
And sure, you can use an application container. But you can also embed a webserver. E.g., we Jetty embedded and use a strict SecurityManager policy[1]. So it's more like:
Code -> JVM (with security manager)
[1] http://docs.oracle.com/javase/tutorial/essential/environment...
I'm in the middle of porting Juju, a pretty huge Go program, from linux to linux and windows, and almost all the changes necessary are not things that a VM can help with, like "cloud init doesn't exist on windows" and "unix pipes don't exist on windows" etc.
For everything else, the Go runtime really does a pretty good job of abstracting away the differences.
Is there any reason to use RVM, PVM on production while Go does not required one?
I believe should be install one and only one Ruby/Python version on production.
Why Ruby/Python does not required application server like unicorn/wcgi, etc?
The article clearly try to make other deployment more complicated.