I say this not as an excuse, but as an explanation: these things are very, very hard to get right, and can be nearly impossible to retrofit onto existing systems. When every single one of your dozens (or at Google's scale probably hundreds) of interlocking backend systems designed at different periods by hundreds of different engineers were built on the assumption that one primary key == one account == one user, and you try to change those assumptions in anything more than a superficial way, it's a guaranteed multi-year project with a high chance of failure. Just look at the mess Microsoft is in with their accounts, also on the front page, as an example (https://news.ycombinator.com/item?id=14159085).
And of course, once you're a certain size (that Google passed more than a decade ago), you pretty much lose the opportunity to ever start over from scratch on this sort of thing. You're dealing with legacy systems forever.