There's a quiet crisis happening in how we store our digital lives, and almost nobody is talking about it. An entire generation is growing up without a mental model of what a file is. They have Google Docs, Notion pages, Instagram posts, iCloud photo streams, and Spotify playlists — but ask them where any of it actually lives, and the question doesn't parse. This post, judging by title and author, is a manifesto for the humble file: a discrete, portable, named thing that you own.

Why does this matter to a technical audience? Because we're the last people who still remember. We know that a file is a self-contained artifact you can copy to a USB stick, email to yourself, back up to three different places, and open in fifteen years with software that hasn't been invented yet. A Notion page cannot do any of these things. A Google Doc is a lease, not a possession. When the service dies — and services always die — the "content" evaporates.

The technical implications are worth dwelling on:

• Interoperability — Files travel between programs. Cloud documents mostly don't. A .txt written in 1985 still opens today; a Google Wave doc from 2010 does not.
• Sovereignty — You cannot be deplatformed from your own filesystem. If your Adobe subscription lapses, your .psd files still exist. If your Figma access is revoked, your designs are trapped.
• Composability — Files play nicely with grep, rsync, git, tar, and every other Unix tool built over 50 years. Cloud objects require bespoke APIs, rate limits, and OAuth dances.
• Longevity — Local files have survived multiple decades of hardware and OS transitions. Very few SaaS products have.

What makes this post interesting isn't nostalgia — it's a design argument. The file abstraction is one of computing's genuine successes: a universal, tool-agnostic unit of persistence. We are actively regressing away from it, and most people don't notice because the alternatives feel more convenient in the moment. The convenience has a bill that comes due later, usually when a company pivots or shuts down and your work is suddenly held hostage inside a proprietary format nobody else can read.

Worth reading if you've ever felt uneasy watching a family member's "photos" live entirely inside an app they don't understand and can't export.