Fuck the cloud (2009)
Skepticism toward “the cloud” resurfaces around a 2009 essay arguing that users should keep local copies of their data instead of trusting centralized platforms. Many commenters describe a revival of self-hosting and homelabs, motivated by concerns over lock‑in, rising costs, service shutdowns, and loss of control over personal archives, while others counter that cloud services have delivered enormous convenience and reliability for non‑technical users. The exchange highlights a growing tension between local‑first computing and dependence on large providers, as well as calls for tools that make self‑hosting or local‑first apps as easy as today’s SaaS.
Meta and “hug of death” irony
- Original article has been posted to HN multiple times over the years.
- This repost quickly overloaded the author’s server (“resource limit reached”), forcing people to use archive mirrors.
- Many highlight the irony of a self‑hosted, anti‑cloud rant failing under sudden load.
Cloud value vs. risks
- Some argue the rant has aged poorly: cloud services have given ordinary users long‑lived storage and easy backups (email, photos, files) that most would not have maintained themselves.
- Others counter that many technically inclined users do keep decades of data locally (documents, email, photos, chat logs, game saves, music) and use cloud only as an additional copy.
- A key distinction is made between:
- Using cloud as offsite backup for data you also control locally.
- Depending entirely on cloud apps and “walled gardens” where export and migration are hard.
Open source and cloud concentration
- Debate over whether “most cloud tech is based on open source”:
- One side says cloud providers sit atop large open‑source foundations (Linux, etc.).
- Another argues the proprietary layers are where most value and lock‑in reside, with “special sauce,” opaque billing, and little compensation to original OSS authors.
- Concerns about centralization: a few massive providers wield disproportionate power, and migrating between them is costly.
Self‑hosting and homelabs
- Many describe homelabs and local‑first setups as a return to earlier, more fun, more autonomous computing: running Proxmox, NAS/RAID, local media servers, DNS, backups, etc.
- Some emphasize how cheap and modest hardware can be (used desktops, mini‑PCs, Raspberry Pi), contrasting this with overbuilt “rack porn” homelabs.
- Others push back: outside tech circles, even basic self‑hosting (Docker, backups, firewall rules) is far beyond what most users can manage. Cloud won because it’s easy.
Making self‑hosting easier / local‑first software
- Several commenters see promise in:
- Local‑first, end‑to‑end encrypted sync tools that hide complexity.
- Appliance‑like systems (e.g., Proxmox‑based or similar) and curated stacks that could eventually be “grandma‑proof,” potentially aided by software agents/AI.
- There is separate praise for traditional desktop/local apps (one‑time purchase, offline, local data) as a middle ground between SaaS lock‑in and full homelab complexity.