We use per-project work spaces too and it has simplified a lot of things for us. The biggest reason for this is that our projects aren't just Go based, their ar

We use per-project work spaces too and it has simplified a lot of things for us. The biggest reason for this is that our projects aren't just Go based, their are other languages in there, many different file types. Building the project doesn't mean running "go build", that's just one component of a much larger code base. A complete build for a web application means: * compile the Go app * compiling the Sass files down to CSS * combining and minifying Javascript files * minifying HTML files * optimizing/compressing image assets * etc. These things need to happen together, and than are organized into the deployable file structure. Ofcourse this is all automated with scripts, but a single global Go workspace doesn't cut it. It assumes that the Go app is king, while in reality its just another component.