It's the other edge of the monorepo/standardized tooling sword. You get nearly unlimited access to the work of people who have come before you, but separating

It's the other edge of the monorepo/standardized tooling sword. You get nearly unlimited access to the work of people who have come before you, but separating your work from the internal commons is no small task. I suspect most Google projects would be non-trivial to open source (even without legal concerns). Building software with Google's internal tools is very different than what's popular in the open source world. It cuts both ways: Many open source tools would be difficult to use at Google, because they presume open source tools and package managers that don't have equivalents in the Google codebase.