Argues that modern AAA physical discs are effectively shells containing installers that pull the real game from publisher servers, meaning the buyer never gets a durable copy regardless of format. Points to Activision account gating on Call of Duty discs as proof that the disc-vs-download frame is obsolete — what matters is whether the license can be revoked.
Extends the argument with 2024-2025 receipts: Ubisoft's revocation of The Crew, Sony's attempted PSN Discovery pull, Nintendo's 3DS/Wii U eShop shutdown, and PlayStation's explicit 'licenses not property' terms. Concludes that neither disc nor download gives you durable software because both sit behind a switch the seller controls.
Broadened the frame past gaming, citing Amazon's remote deletion of Kindle books (including the infamous 1984 incident and ongoing quieter removals), movies vanishing from iTunes libraries when regional licensing lapses, and Google Stadia as a rare case where refunds actually happened. The underlying critique: 'buy' has been redefined across the entire digital economy to mean 'rent until the seller decides otherwise.'
Point to the Stop Killing Games European Citizens' Initiative crossing one million signatures in mid-2025 as evidence that revocable-license outrage is no longer a niche gamer complaint but a mainstream consumer-rights issue. Argue that voluntary industry fixes have failed and only legislation forcing publishers to leave games playable after server shutdowns will change the incentive structure.
A bearblog post titled "It's not about physical vs. digital games, it's about ownership" hit 366 points on Hacker News, restarting an argument that most gamers thought was settled a decade ago. The author's point is blunt: the physical-vs-digital framing is obsolete, because the physical copy is a lie. Most AAA discs today ship a small installer that pulls the actual game from a publisher's servers. Buy the Blu-ray of a modern Call of Duty and you're still bound to Activision's account system, still subject to the license terms, and still one server shutdown away from a coaster.
The post lands in a year full of receipts. Ubisoft revoked access to *The Crew* in 2024 after taking the servers offline — a game people had paid up to $60 for, gone from their libraries with no refund. Sony tried to pull purchased Discovery content from PSN accounts in late 2023 before backpedaling under pressure. PlayStation's own storefront terms explicitly state that purchases are "licenses," not property. Nintendo shuttered the 3DS and Wii U eShops in March 2023, cutting off legal access to hundreds of titles that were never re-released. The disc-vs-download debate misses the point entirely: neither format gives you a durable copy of the software you paid for, because both are gated by a license that the seller can revoke.
The HN thread pushed the frame beyond games. Commenters pointed at Kindle books Amazon has remotely deleted (the 2009 *1984* incident is now folklore, but it keeps happening quietly), at Google Stadia refunds that at least happened, at movies vanishing from iTunes libraries when regional licensing lapses. The 'Stop Killing Games' initiative — a European Citizens' Initiative that crossed the one-million-signature threshold in mid-2025 — is the political expression of the same frustration. It's aimed at games, but the underlying question is bigger: what does 'buy' mean when the seller keeps the off switch?
For developers, this isn't just consumer-rights noise. It's a design constraint that's quietly reshaping how software gets built and shipped. Every time a publisher yanks a title, they train the market that 'buy' means 'rent until we're bored,' and that lesson is starting to price into what people are willing to pay.
The economic argument used to be that always-online DRM was strictly better for publishers — piracy down, telemetry up, live-service revenue on top. That calculus is shifting. GOG has quietly built a preservation program specifically to onboard games whose publishers have gone under or lost rights, and it's a marketing story now, not a footnote. Itch.io's revenue split (developer sets the cut, default 90/10) plus its DRM-free-by-default posture has made it the actual home of indie distribution while Steam holds the top of the funnel. Even Valve — the company that arguably invented modern software licensing at scale with Steam — added a disclaimer in October 2024 clarifying that Steam purchases are licenses, after a California law forced storefronts to stop using the word "buy" for digital goods that can be revoked.
The technical parallel for anyone building SaaS or dev tools is uncomfortable. If your product is a monthly seat license with cloud-only state, you are one funding round or one strategic pivot away from being The Crew for someone's workflow. JetBrains learned this when it moved to subscriptions in 2015 and had to introduce the "perpetual fallback license" — pay for 12 months, keep offline access to the version from a year ago — because the community revolted. Adobe did the opposite and never blinked; the market accepted it because the alternatives were worse. Figma users learned it the hard way when the Adobe acquisition was announced (and again, differently, when it was called off). The pattern is the same one gamers are complaining about: you pay, you use, someone else decides how long the arrangement lasts.
There's also a preservation angle that matters more than it sounds. Cloud-only games are already partially unpreservable — the server binaries usually don't get released, and reverse-engineering server emulators (as the *City of Heroes* and *Star Wars Galaxies* communities did) takes years. Extend that logic to CI systems, ORMs, auth providers, and internal tools that live entirely in someone else's cloud, and you get a software industry with the memory of a goldfish. Nobody can run a 2015 stack the way they can boot a 2005 Linux ISO in QEMU.
If you ship consumer software, the market is segmenting. There's now a real, growing customer base that pays *more* for DRM-free, offline-capable, exportable software — and treats "we might turn this off" as a disqualifier. GOG's catalog, itch.io's indie scene, Obsidian's local-file Markdown model, Standard Notes' end-to-end-encrypted plaintext, self-hostable Ghost — these are all commercially viable products whose pitch is a variation of "we can't take this away from you." That's a wedge worth taking seriously if you're competing against an incumbent with a phone-home architecture.
If you build B2B tools, the practical move is boring: document your data export path, make it work end-to-end, and treat 'takeout' as a first-class feature rather than a compliance checkbox. The teams that will actually stick with you through a pricing change or an acquisition are the ones who *know* they could leave. Everyone else is a hostage, and hostages churn hardest when the ransom note arrives.
And if you're an engineering leader making buy-vs-build calls, run the 'server shutdown' thought experiment on every SaaS in your stack. What breaks if the vendor is acquired and sunset in 18 months? What's the recovery plan when your CI provider raises prices 4x, as several have this year? Building a business on rented infrastructure is fine; forgetting that it's rented is not.
The consumer-facing fight — Stop Killing Games, California's SB 2426, the FTC's ongoing interest in "click to cancel" — will keep moving, and it will bleed into software categories beyond games as legislators notice the pattern. Expect more storefronts to be forced to say "license" instead of "buy," more mandated end-of-life plans for online-only products, and more class actions when publishers pull the plug without one. For developers, the useful reframing is that ownership isn't a nostalgia issue — it's a design property. You either build systems that keep working when the vendor doesn't want you to, or you don't. The users who care about the difference are done arguing about disc drives.
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.