• Videos I need to watch for class.
• PDFs I need to read for class.
• Word documents I am writing for class.
• Photos, videos, and audio recordings I will use to write papers for class.
The "iOS model" would have me segment all of this data by file type. The PDF from New York State on K-12 educational standards would be next to my 2021 tax returns. My paper on single-sex schools would be next to the technical documentation for a web app I'm developing. This would be terrible.
Files need to be organized by purpose, not file type. I know what my files are for. My computer does not.
This is also a major reason why I hate my iPhone.
All that said, I do agree with the general premise that files should be organized in reasonable places by default and users should be able to override that should they see the need.
Contrast this with traditional OS X. I can open a file in any app, but the file continues to live in Finder. In a way, you could say that the Mac puts files first in the way that iOS puts apps first. An app is just a tool, and could be used for anything: I write papers for school and documentation for work and poetry for pleasure. A file, on the other hand, has a distinct purpose.
I’m not saying the final solution to data organization is just “all Images in one directory”. The solution is one where you don’t worry about directories and still easily find and group the data you need.
Windows had grand plans for this that were scrapped. Understandably, but also sadly.
Oh, I absolutely agree! But as I said, I know what my files are for, and my computer does not. So until we get some incredible AI that not only understands the context of every file but can also use that context to make perfect organizational decisions, I expect to be the one responsible for grouping my data.
To be clear, I don't think directory hierarchies are necessarily the be-all end-all of digital organization. For example, I like the idea of organizing based on tags, because a lot of documents rightly belong in more than one category. However, I expect I'll need to be the one who sets the tags.
iOS's solution does work better on mobile than on desktop (and iPad), although I do run into problems on my iPhone.
And yes, of course no one should be stopped from having one area where they have a word document, six images and a text file. OF COURSE. But whether that's a directory or not isn't what's interesting. The interesting part is that I can group them together logically, find and use them easily etc.
The second best is a fully manual directory structure with no “surface” added. But this is not nearly as good for the average user.
By far the worst one is what you get when you (correctly) like Microsoft realize you are in the second category but you’d like to be in the first. The end result is an annoying middle ground that has plagued windows for a long time now. They probably (incorrectly) assumed they could get to the iOS situation eventually.
Separating the application and its binaries isn’t a bad idea though. I don’t want to back up applications, just their data, for example. And I want to be able to have different permissions for the app binaries and elsewhere. So programs\Quicken and data\Quicken would be better than the other way around. And this isn’t far from what windows does. If I create an app I put the user data in %appdata%\myprogram. The folder is annoyingly hard to find though but that’s more an explorer UX issue than a problem with how the files are stored.