GitHub Thought Developers Wanted Their Code on CD. The Backlash Was Instant.

You could almost hear the collective groan from every developer Slack channel on Earth.

GitHub — the platform that literally defines modern software collaboration — decided it would be a good idea to offer burning your repositories onto physical CDs. You know, those shiny plastic discs that peaked in relevance around 2003. The ones your parents used to store family photos before iCloud existed.

The internet’s response was swift, brutal, and entirely deserved.

When a platform that sells the future tries to nostalgia-bait you with the past, it’s not a feature — it’s a confession that they’ve run out of ideas.

Let’s be clear about what happened here. This wasn’t some rogue engineer’s side project that accidentally shipped. Someone at GitHub — likely several someones — sat in a room, discussed the idea of putting source code on compact discs, ran it up the flagpole, and nobody saluted. Except they shipped it anyway.

The mockery came in waves. Developers posted photos of their CD collections from the 90s. Someone joked about floppy disk support being next. Another asked if GitHub would also include a free dial-up modem with each order. The humor was sharp, but underneath it ran a current of genuine irritation.

Because here’s the thing: developers aren’t laughing because CDs are old. They’re laughing because the entire premise reveals a stunning misread of what they actually care about.

Modern development is built on speed. You push code, CI runs, tests execute, deployments happen — sometimes hundreds of times per day. The workflow is collaborative, ephemeral, and cloud-native by default. Nobody wants a static snapshot of their repo burned onto a physical medium that will degrade, get lost, or end up in a landfill alongside the AOL trial discs of yesteryear.

Developers don’t want artifacts. They want velocity. They don’t want souvenirs. They want their tools to disappear into the workflow so completely that they never have to think about them.

So what was GitHub actually trying to do? The charitable read is that this was a low-cost marketing stunt — a bit of whimsy to generate buzz. The less charitable read is that someone in product saw an opportunity to upsell a premium tier with a gimmick bolted on, hoping nostalgia would override common sense.

Either way, the backlash exposed something uncomfortable. When platform companies grow large enough, they start building for their own amusement rather than for the people who actually use their products. The gap between “what looks fun in a roadmap meeting” and “what solves a real problem” widens until you end up shipping CDs in the age of serverless.

You’ve probably felt this yourself. The tool you depend on adds a feature nobody asked for while the bug you reported three years ago still sits in the backlog. The product team is busy chasing engagement metrics and press coverage while the actual users are quietly migrating to alternatives that respect their time.

The most dangerous thing a platform can do is confuse its own cleverness with its users’ needs. GitHub just learned this the hard way — in public, on a Tuesday, with the entire developer community watching.

The CD offer was pulled. The mockery will fade. But the lesson should stick: when you build for a community, you don’t get to decide what they find valuable. They do. And if you forget that, they’ll remind you — loudly, publicly, and with exactly the kind of dark humor that makes the whole thing go viral.

Because developers have always had one superpower that no platform can replicate: they know exactly when they’re being sold something they don’t need. And they will never, ever let you forget it.