This makes sense for engineers but is detrimental from a user point of view. Google effectively taking what would be a few days of engineering time to update some API calls and instead amplifying it and passing it on to users.
When considering whether to learn/migrate to a Google service, everyone should consider this ratio at which Google values your time vs. that of their engineers.
If something that relies on say, one of their log services, and that log service is getting end-of-lifed then all the dependent services that aren't really critical will also get shutdown. It's a forcing mechanism to keep the amount of cruft down. If that service that relies on the old service is that important they'll put the resources on the project long enough to port it to the new service.