Don’t forget that there’s a hidden system junction at C:\ProgramData\Application Data that points to C:\ProgramData. Because everyone loves loops in their filesystem. Of course C:\Users\All Users is also a junction to C:\ProgramData. This kills updatedb in WSL.
Always remember, C:\ProgramData is the eqivalent of /etc in Linux. If they don’t know where to put/hide shit, but needs admin priviliges to edit and users can only read, you put it in C:\ProgramData.
Config files that are meant to be used as sane defaults for new user accounts, yes. Config files that are meant to be manually edited, no.
Besides, there are a lot of examples of configs that are saved in ProgramData, like, let’s say, registration info for proprietery programs (of course, this info needs to be shared amongst users, so your safest bet is ProgramData). Hidden by default, makes it perfect for storing everything the program is trying to hide from the user.
Agreed, but the number of places where to search for the config is not as big as in Windows. And there is the fact that most software is open source, so you could always check where the application saves it’s data.
Game save data? No, my documents.
Application config files? Again, my documents.
Temporary documents I don’t care about keeping? Downloads, duh.
My actual documents? Desktop.
My desktop? Turned icons off because it was too messy.
Windows program data file structure has always been the wild west.
Don’t forget about the hidden ProgramData directory at the root of the file system. Ableton Live likes to install there for some ungodly reason.
Don’t forget that there’s a hidden system junction at
C:\ProgramData\Application Data
that points toC:\ProgramData
. Because everyone loves loops in their filesystem. Of courseC:\Users\All Users
is also a junction toC:\ProgramData
. This kills updatedb in WSL.Always remember,
C:\ProgramData
is the eqivalent of/etc
in Linux. If they don’t know where to put/hide shit, but needs admin priviliges to edit and users can only read, you put it inC:\ProgramData
.I think programdata is closer to /usr/lib or maybe /var/lib.
You almost never see config files in programdata.
Config files that are meant to be used as sane defaults for new user accounts, yes. Config files that are meant to be manually edited, no.
Besides, there are a lot of examples of configs that are saved in ProgramData, like, let’s say, registration info for proprietery programs (of course, this info needs to be shared amongst users, so your safest bet is ProgramData). Hidden by default, makes it perfect for storing everything the program is trying to hide from the user.
System wide config for an application? Lets put that under C:\users*????
And Linux isn’t? There’s definitely not a central location either.
Agreed, but the number of places where to search for the config is not as big as in Windows. And there is the fact that most software is open source, so you could always check where the application saves it’s data.
Yeah, the Documents config file/dir pisses me off the most as well!
Game save data? No, my documents.
Application config files? Again, my documents.
Temporary documents I don’t care about keeping? Downloads, duh.
My actual documents? Desktop.
My desktop? Turned icons off because it was too messy.
Just another day using Windows…