Great article (so far…49mins is a long time at the office!). Thanks for breaking this all down. Quick thought on central package registries:

I think Go could really use a central registry. Although Go has the advantage over other languages in that the package location can be discovered via source code there’s no guarantee (or even a trustworthy promise) that a package will remain there. Several popular packages have so far moved from Labix or Bitbucket over to Github. There’s also MDK events like what happened with Google Code. My sense is that if a tool such as glide could be configured to “get” packages from the registry you could effectively eliminate such problems.

I’m curious if you agree with that opinion and, if so, what you think the major challenges would be in creating such a registry.