Advantages of monolithic version control
danluu.com
danluu.com
At Google this regularly failed. We spent hours unable to commit changes (unless a disaster could justify ignoring build and test failures) because someone we'd never met had broken the world and the fix was still making its way through the enormous backlog of projects to retry. Every project needed people taking turns in a "build cop" role diagnosing this stuff and demanding rollbacks as quickly as possible.
It's essential to pin known-good version of your dependencies and upgrade when you can handle it. You can't expect every commit anyone ever makes to be production ready.
Of course not — but surely that's what branches are for.
Does Perforce not have a concept of branches? It seems absurd that Google would let folks merge untested commits into master.