I'm guessing they are referring to how Google uses Blaze (internal version of Bazel) to build Go binaries, not the 'go' command and it's modules.
The first time I went to work on a personal project using Go after I joined Google, tried using Bazel because I was so used to Blaze and I liked it a lot. I was very disappointed to find that the integration between Bazel and Go was severely lacking and required me to use third party extensions to get things working as expected, which was quite disappointing. That was a few years ago so things might better now
The first time I went to work on a personal project using Go after I joined Google, tried using Bazel because I was so used to Blaze and I liked it a lot. I was very disappointed to find that the integration between Bazel and Go was severely lacking and required me to use third party extensions to get things working as expected, which was quite disappointing. That was a few years ago so things might better now