Dear Google Cloud — cover art: a badger in a waistcoat at a lamplit study desk, reading a deprecation notice decorated like a Victorian valentine ('Besties Forever'), a rack of identical letters beside him. 🔮

2020 · Medium · Essay

“Some folks believe that platform developers should shoulder the costs of compatibility, and others believe that platform users (developers themselves) should bear the costs. It’s really that simple. And isn’t politics always about who has to shoulder costs for shared problems?”
— From Dear Google Cloud: Your Deprecation Policy Is Killing You
Read the essay

© 2020 Steve Yegge. Originally published at Medium.

Author’s note

I confess to re-reading this occasionally as a guilty pleasure.

This is some of my finest work. Solid thesis, and one that afaik nobody had ever tackled before. Namely, that deprecating your APIs loses you users each time you do it, whereas maintaining compatibility retains them by default.

AI Notes

The "Besties Forever" essay opens with a story from Steve's early Google days: a Bigtable instance he spun up for a 2005 codelab and forgot about, still quietly running two years later — until the Bigtable team emailed him personally by name, offering to help him upgrade off an old binary. That's the standard the rest of the essay measures Google Cloud against. The letters from GCP are the opposite — cheerful, decorated, signed "Besties Forever," announcing that a service he depends on is being sunsetted, the replacement is an undocumented beta with no migration path, and the rework is his problem. He gets one about once a month. Backwards compatibility keeps systems alive for decades. Emacs still runs extensions Steve wrote in 1995; when Emacs marks an API obsolete it means you probably shouldn't, where Google's deprecation means we are breaking our commitments to you. A platform that breaks your software on a yearly schedule is selling you a used car it knows will fail inside a thousand miles.

Related listings

  • 2011

    Stevey's Google Platforms Rant

    The essay this one points back to — "I've ranted about Platforms before." The 2011 rant diagnosed Google's blind spot for platforms; this one watches that same blind spot break customers' software on Google Cloud.

  • 2026

    Software Survival 3.0

    The same argument, six years on and generalized: software survives when it earns its keep, and backwards compatibility is one of the things that buys a tool decades. Git, grep, and Emacs are the survivors in both essays.

  • 2018

    Why I Left Google to Join Grab

    The other side of the Google-alumnus frustration, written two years earlier — why the place he admired stopped being the place he wanted to build on.

Where it was argued