Dear Google Cloud, Your Deprecation Policy Is Killing You

A rant Steve swore he had no time to write; it opens "God dammit, I didn't want to blog again" and never really cools down. The genre is frustrated alum. Twelve-plus years inside Google taught him how good the internal engineering culture is (the opening anecdote, about a forgotten codelab database and an email he nearly deleted as a form letter, is a small love letter to that era), and running his online game on GCP taught him what the same company feels like from the paying side of the counter. Under the profanity sits a real comparative tour of how Emacs, Android, Java, and the web browser each treat their old APIs, plus a firsthand Foo Camp story about Guido van Rossum and Python 3 that is worth the visit on its own.

Halfway through, Steve confesses to a role in the crime: he built Grok, the code-understanding engine that made Google's fleet-wide automated refactoring possible, so the internal habit he is flaming is one he helped arm. He is also honest about the evidence — no slam-dunk proof, just thirty years of accumulated examples, and his kinder reading of AWS is admitted speculation. The piece kept growing after it landed. As the discussion threads filled up (two are linked below), Steve appended postscript after postscript, correcting himself, retracting a detail about gummy sharks, and picking up one late anecdote that makes his case about Google support better than anything in the essay proper.