Networked machines. (Aside from the obvious security problems on a multi-user installation.) The "gawd knows where hidden directories" (of which there are two, %APPDATA% and %LOCALAPPDATA%, plus, on a recent Windows version, a number of compatibility links and some sort of integrity level thing) are segregated into the part which should have an authoritative copy on the file server ("roaming") and the part that can or has to stay on the workstation ("local").
And you aren't the only user on pretty much every OS. There are many many many built in "users" for different internal operations.
Your user should be the admin, shouldn't be tied a profile etc. Linux is setup like more like this.
Yeah, it makes it more complex for certain network style things (you have 4 computers and want to sync between them), but it's trivial to work around.
The reason Windows is built like this is they develop first for enterprises and libraries, everyone else gets the shitty castoffs...
Android has been copying Apple in that it now also has automagic folders and file managers. I also remember Google doing some idiotic A/B tests some moons ago of hiding the actual page result URL, it was one of the reasons (on top of search quality) that I stopped using it.
On Android you now have to go through multiple settings to enable explicit paths as if was somehow an 'advanced' feature to show an explicit file path.
I assume it is mostly driven by UX somehow it is now an agreed truth that file manager abstractions are too complex for the average user to grasp therefore must be vigourously hidden at all cost.
Or to people in different age brackets: for a few years now, people have finished uni while doing all their work on phones and tables without a desktop OS involved. No files, no desktop, no actual applications. We should stop copying desktop mentalities into modern workflows.
Or the other way around: nobody has desks or paper folders in file cabinets anymore, nobody needs to physically handle files and organise them, nor do their have boxes for physical mail that comes "in" and goes "out". We should stop copying legacy office concepts into software.
They aren't morons. They don't necessarily understand all the complexities, like aliased folders, etc., but that's because they don't need to and so haven't tried.
But parent is right. Nobody is out here maintaining and pruning their beautiful directory hierarchy, and complaining about how messy applications make their home directory. Because nobody turns on “show hidden files”. Nobody cares.
These are organizational concepts, not software concepts. People, even mobile uni students, have and must master them. As a result they get reinvented constantly in/as apps.
What people are mad about is people are told 'this is how you will organize' rather than just learning to organize. It is absolutely fucking stupid.
So actually the problem is worse. Apple is schizophrenic about folders and leaves their users with the cognitive dissonance.
Most systems have or used to have tagging functionality as well, but apparently that wasn't used all that much either for information classification and organisation.
Granted, I can't read minds and I don't know what everyone everywhere does, but I do see large scale changes in employee instructions for new hires, university hires and even in cross-org/education projects. For most young/new people, their phone was their first 'computer' and the 'default' environment, and a desktop is the anomaly. People looking up how to do things on ticktock is not a funny meme, it's reality and seriously tainting the knowledge of junior hires on the lower end jobs (like entry level service desk backoffice). Knowing where to find authoritative information, how to verify it, and how to use that as a reference to validate and find other information seems to be a foreign concept to some as well. Even something like a somewhat specific google search or wikipedia article and the references it can supply are not as normal as one might think, and the gap is getting bigger, not smaller.
Knowing how to store, organise and retrieve information, regardless of what system is used (including computers, file cabinets and archive rooms) is a skill that doesn't just magically appear in your brain, you have to actually observe, trial or classically learn about it to make use of it. It used to be through day-to-day tasks and a growth in responsibilities when growing up that people got that skill semi-automatically, but that is no longer the case.
When they want to find stuff, they just search for it in the file picker. Or hopefully the file picker is just already in the right place. Often this UX is kinda bad, and it's hard to find things. Sometimes they give up, and either do without, or (if applicable) visit a website to just re-download whatever they can't find. Or they ask a technically-adept friend to help them.
Carefully creating a directory hierarchy and actively picking and choosing where to put things when downloading or saving files is just not a thing most people do.
Windows has an existing convention for this, like Linux's XDG. Imagine if you looked at your Linux filesystem root and saw /boot, /dev, /usr, /tmp, and /Quicken.
You'd probably see a /Quicken/ as well as a file /Quicken-uninstall as a broken symlink to nowhere.
I helped my wife reorganize many hundreds of images. Finding out where they really were located and where they would actually end up was a tremendous chore, and locating them again has continued to be difficult.
Even doing a backup is stressful. Where are the files really located?
I suppose I could create some automation tools, and I have thought about that.
macOS is the same.
Also, don't use 14 years old EOL systems.
Beyond that, getting a full path is trivial (realpath) and figuring out which block device backs it is also quite straightforward (findmnt).
There are also strange constructions that don't actually correspond to a single folder, or at least there were the last time I used Windows which was quite a few years ago now. A place that looked like a photo directory in Explorer, but actually it was a view of multiple directories and I don't know where stuff ended up if you copied into it.
The Explorer does not browse the file system, it browses a graph of (COM) objects called the “shell namespace”[1], and has been since Windows 95. Notable examples of non-filesystem nodes include My Computer, Recycle Bin, Control Panel, and Network Neighbourhood; a more obscure one is the All Tasks (“god mode”) collection of all settings applets that exists so that the Start menu can search it[2].
I actually think it’s neat how seamlessly this approach has been integrated—we don’t usually think about it even though we actually encounter it all the time. Microsoft’s attempts to extend this to a full-blown object-oriented (Cairo) or relational (Longhorn) filing system were always so muddled I don’t really get what the actual idea was, though.
[1] https://learn.microsoft.com/windows/win32/shell/namespace-in...
[2] http://brandonlive.com/2010/01/04/the-so-called-god-mode/
Contrast to windows where your "Documents" folder might be getting backed up via one drive or roaming profile, or it might just be local disk on that machine.
In my experience for a corporate windows environment its best to map a H: drive to a network home drive share and get users to always save in there - if its not mapped it means you are probably on misconfigured host.
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.
• 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.
I really really dislike Windows when it hides paths, for example, "My Pictures". Where the heck is that?
This lunacy infects Windows applications, like Quicken and Thunderbird, which spew themselves and their data into gawd knows where hidden directories. Why can't they simply do the obvious? Create a \Quicken directory in the root, and have a \Quicken\program and \Quicken\userdata ? But noooo.