That's until you start thinking about dependency versioning. The only way I can think of how to integrate versioning into Go's "one workspace" philosophy is to

That's until you start thinking about dependency versioning. The only way I can think of how to integrate versioning into Go's "one workspace" philosophy is to encode versions into package paths and then use import aliases to point to different versions of packages. But that means you're spreading versioning information across all source files, and it only works if everyone decides to use this approach. So far no one does (I believe).