The file system is quietly disappearing from consumer software, and nobody seems to mind
There was a time when every application expected you to decide where something lived on your hard drive. You'd hit Save As, navigate to a folder, name the file, and you were done. The file was yours — a real thing in a real location you could find with any other program.
That model is vanishing. Mobile apps never had it. iOS and Android treat the filesystem like plumbing you shouldn't have to see. But it's spreading to desktop too. Cloud-native apps save to "the cloud" with no local file at all. Even traditional desktop software increasingly defaults to auto-save into an app-specific vault rather than letting you pick a path.
The trade is framed as convenience, and honestly it mostly is. Nobody misses the "you have unsaved changes" dialog. But something gets lost: the file system was the one place where every program spoke the same language. A .txt was a .txt whether you made it in Notepad or vim. A folder could hold outputs from five different tools, organized however you wanted. That interoperability was free and universal.
What replaced it is a collection of app-shaped silos. Your notes live in one app's database, your documents in another's cloud, your photos in a third. Moving things between them means export-import rituals that each app makes slightly different and slightly annoying — on purpose, probably.
The people who notice are mostly developers and power users. Everyone else just adapted. But I wonder if we're raising a generation that genuinely doesn't know what a file path is, and whether that matters.
0 replies