This means streamlining platforms and trimming excess/old code.
I've seen 'code debt' and 'technical debt' mentioned more than a few times in this thread and I think these are why Google is so aggressive about dropping support for things. They don't have time, and the engineers don't want to be forced into someone else's pet project (face it, that's where a lot of these platforms and features come from).
So they cut their losses and rise.
From the other thread, pretty usual recently
> I considered working at Google last year after a recruiter reached out to me, but their decision to backtrack on their promise in China changed my mind
Maybe it's not about rising anymore.
To borrow a famous quote, Google is like an ship with a hole in the bottom, leaking water, and they seem to be trying to get the ship pointed in the right direction.
Still, whilst the ship's not yet overrun, I can't blame the individual teams for trying to throw as much water back overboard as they can muster.
That's why Google Reader is gone, I suppose. Google just couldn't save it, no matter how much money and engineers' time was spend on it. And we all know how much exactly it were.
> Rather, I think that removing annotations is a good sign that Google is trying to do something smarter: manage the scale of YouTube.
Consistently removing the features which is not popular among majority of users is not smart at all. That's the dumbest way to manage the scale actually.