1767
please
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Jul 2024
1767 points (98.8% liked)
Memes
45755 readers
989 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
Do you mean the byzantine directory structure for system files? The default of installing to "Program Files" doesn't seem too unusual, although adding "x86" bit seems unnecessarily complicated for a typical end user. Same with the rest of the standard directories that people use most often.
The directory structure for system files is bad, but that's true for Unix-derivatives too. Unix has /bin and /lib, /sbin, /usr/bin, /usr/lib, /var/opt, etc. Different versions of Unix have different ideas of what belongs where. Even different flavours of Linux have their own ideas.
At least with Linux the distro-specific packages install software where it should go.
On Windows you end up with 32-bit binaries in the 64-bit Program Files folder, and vise versa. You end up with files saved arbitrarily to three different application data directories, and sometimes your Documents folder, so sometimes the registry, why not? Should we put several folders full of drivers directly on the root of the C drive? Of course, where else would they go?
I keep explaining this to my grandmother but she just stares at me and says "When I was your age, we wrote things down in our Trapper Keepers"
Mostly for user files.
For system files it's not too bad. At least there's some logic to it.