On the other hand, Google is notorious for EOLing services that don't have a billion users, even compared to other cloud/web companies. That should be priced in.
Maybe they're mostly running their cloud to iron out the kinks im the API's they use themselves?
Thats a little extreme.
10 years ago was 2007. So you have code written in 2007 still in production? Less likely, but I bet there are enough "yes" answers out there.
I'll give you one guess what sector :D
I would certainly hope people have upgraded to newer tools than those.
What I'm saying is, those things are all still running in prod. I got an employer off Java 6 just two weeks ago. The next step is all the Java packages that were deprecated 5 years ago.
If you truly want API longevity at that scale, we probably need some force beyond that of quarterly-profit-driven companies to actually achieve it. Maybe some nonprofit (the Internet Archive, maybe) could offer "API insurance" packages, where—in exchange for your premiums—they'd build and maintain API-compatible replacements for any and all services the insurance-holders rely on, if said services should happen to die.
Then you'd just need to insist (with force) that all network-RPC-based "client" libraries have configuration to let you easily change their endpoints and expected X.509 trust anchors...
1. Take a talented, valuable developer off whatever important task they're working on now.
2. Get them review whatever changes have supposedly been made between old version and current version.
3. Get them to read the existing code and think about places where it may break. (Often not obvious.)
4. Deal with doing the upgrade, which may often have dependencies that can break other unrelated things.
5. Write whatever code needed to make changes. (Often not obvious.)
6. Test on some sort of staging setup, which was probably written by some other person a while ago and may or may not have adequate coverage for this specific feature (since it was already working!!!).
7. Deploy and test in production.
8. Hope and pray nothing breaks.
All of that work (time and $$$) must be done to achieve ZERO benefit for your customer. High cost! Zero benefit! That makes developers (and founders) angry.
1 year deprecation is insanely short for public-facing infrastructure APIs. We should be talking about 10 years.