Sure it does! Throw that festering pile of garbage into a docker container and keep it away from everything important while bind mounting the arbitrarily-placed config directory in the container to something sane on the host.
This should be considered a war crime, and doubly so when they don't even have the decency to prefix it with a dot (looking at you Golang). It's my home folder, not a dumping grounds for random trash.
Or in /etc/<application>, or in /var/<application> I've seen all of that, sometimes differing between distributions for maximum annoyance. So I don't think we get to act smug in I'm this particular case.
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.
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.
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.
Or if you still want a start menu, Start11 is worth paying for to get away from Microsoft's ad-ridden crapware they call the start menu. It even supports using Everything for showing file results.
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.
Don't forget %USERPROFILE%/AppData/Local/Programs, where some programs get installed to because the developer doesn't want to make it a system wide installation.
The setting you're looking for could be in %appdata%
It could be in %localappdata%
It could be in C:\ProgramData.
It could be in the registry. It could be in HKLM. It could be in HKCU.
It could be in any of the userdirs.
It could be in the application's directory.
On linux, where the config file for a specific program is, can vary annoyingly greatly depending on what distro you're using and sometimes the same config file exists in several places and somehow certain parts of the configuration parameters get taken from several of those files, so if you think you've found what the actual config file should be and remove the duplicates, suddenly the program uses defaults or doesn't even work at all.
Yup. Is it in /usr /var /etc or /opt? Maybe in some hidden home folder? Sure, you can Google it, but there's no guarantee you'll find the right answer.
There are only a handful of places Windows sticks stuff, and it's pretty predictable.
Disagree. Take game saves on windows. They can be in appdata\local, appdata\roaming, documents\company-name, documents\savedgames\company-name
I'm sure there are more.
Savegame folder is then placed either ina folder with game name or studio name, so easy to check all these locations within minutes.
Let's not talk about rpgmaker games tho. I've seen them do some wacky shit with gamesaves.
Edit: To make my point clearer, I disagree with person above me about their disagreement. Savegames on windows are predictable as hell. Thanks to person below for pointing out I didn't convey. :<
Generally /usr should be managed by the package manager, /etc is for global custom configs and the user home is user specific.
/var shouldn't really be config, mostly logs or webservers for some reason.
Brother scanner utilities: /opt
Pretty sure I had to change something in /usr once, but I forgot what.
Now, /var would be very unusual.
But most of the time, all the configuration files happen to be somewhere in /etc.
Docker on RHEL saves everything in /var/lib, for example. Tenable and Nessus stick it in /opt. I'm currently doing a rhel7->8 upgrade, and that shit gets stuck everywhere.
But, I also have issues on my Pis. For a lot of the packages I use, I'm lucky if they actually put their .service file in /etc/systemd. Having to run a find / command on a pi can take forever.
I don’t know what Tenable and Nessus are. I’m guess you have to install them from outside the package manager or build them from source, in which case, yeah, using /opt for config would be acceptable.
Long read ahead, this resulted in a pretty big rant, but I feel better now:
Windows has way more silly places. From registry to ini files, assemblies, common files, services, drivers...it's everywhere.
Do you know how an MSI packages for software installation work? Let me tell you, it's a mess. An utter and complete garbage format. A database with hundreds of buggy functions, empty lines and internal inconsistencies. There wasn't even a way to create them comfortably without paying for expensive software back then. Yea, im looking at you, flexera admin studio.
I automated hundreds of custom software installations on 2000 clients from windows 2000 to XP to Windows 7 to Windows 10... for >10 years, so I know what I'm talking about.
On Linux 99% of apps save global settings in /etc and usersettings in /home/user/.* or the newer way XDG_CONFIG_HOME.
But since all is a file on Linux every config can simply be copied to restore or backup settings. Almost every tool has man pages. How hard is it to run man tool and read the specifics if you need help? Windows? Sometimes you got some help files in a strange format (.hlp?). Other then that, start the browser and ask Google.
Linux package managing since 2003 has been better then it ever has been on Windows to this day.
One command to update all components? Packages will be installed and removed automatically to fulfill the dependencies of the software you want to install? Every package is build by a trusty maintainer of the OS instead of some overworked windows engineer that needs to create profit.
Do you know how Deb files work? They are simpel zips of the folder structure and files the software consists of. A textfile with metadata like maintainer, name, version and, very important: dependencies. Last but not least there are a two or three files that can contain scripts that need to be executed prior or past installation. That's it. And you can do everything with it.
On Windows you often are forced to find the right combination of weird parameters to ensure a program starts. commandlines like "c:\windows\powershell.exe -e cmd /c program name", happen way more often then you would expect.
On Linux I get: Global package manager and updates with trusted packages, no telemetry, more safety, no ads, better privacy...and many more.
My personal opinion: I don't understand how people can even question the superiority of Linux for personal devices.
Trust me, that is not Linux specific, Windows has that bullshit as well. Everything depends on how the devs wanted to solve the local settings problem, and if you have devs that work 1 or 2 years on the project and then quit, which in turn are replaced by other devs, you get this bullshit. The new ones usually don't wanna touch the old one's code, or if they do, they only make minor changes, just enough to make something that's not working, work.
Sorry, that was my lame joke about the simlar sound of the windows essential tool "regedit".
My only surviving knowledge from when I used to be able to do things on windows was that it was always a bucket of shite until you "regedit" a bunch of things. These edits were arcane secrets known only to mystical internet guru's like some bloke called "Fred Vorck" and impossible to figure out by logic, reason or even through mundane hard work. I assumed that's what the lower panel in the OP is getting at.
But on reflection, I'd be sad if there's not a forum on reddit called "regedit" will all the advice on what registry keys to fix - so unintentionally it might not be the worst advice - apart from the word "simple".
I feel mildly aroused when I see a program or a game that collects everything in it's folder and can be used from a USB drive. Some paid, industrial grade software leaves so much traces and depends on so much different hidden files and keys it's making me sick.
Or if you just symlink /usr, /opt, and /home to that usb drive. You may be asking why you wouldn't just mount partitions on the usb drive to those locations. This is not a question I will be answering
That is good... unless you plan on sharing the app between users, then it sucks, because every user has to be an admin in order to change the config... and then, you have one user that sets it like so and so, and another that sets it completely different. And this is why separate settings for users is a good thing. Sure, have an option for a global config, and let that copy be copied to the local config as sane defaults, but not having the option to actually have separate configs in user directories is, from an IT perspective, insane.
HKEY means "handle to registry key"... Not that that helps anything.
When code opens a file, device, etc, it's given a "handle" to it, which is an internal reference so that Windows knows which file you're reading or writing, and it keeps track of where you are in the document. Similarly, HKEY_CURRENT_USER is the handle that gives you the current user part of the registry.
I know that, the HOTKEY_* part of it was a mystery, why is the key hot... I mean, why does HK have to stand in front of it, it could be simple like just LM, CU, U (Users... still does nothing and nothing in it gets transfered as a setting in new user accounts), CR, etc.
Huh... I don't know where I've read this a long time ago, but I could swear it was HOTKEY, not HKEY... your explanation does make sense though, while what I thought never did make sense.
What the fuck is local low? I don't understand. Local is Billy G's jizz... I get that... And Roaming is for poor plebs. But why LocalLow? Is it like cache? But I have seens games saving their save files there. I don't understand
Roaming: this data can be moved between machines in a domain if you have a roaming profile. E.g. go to another workstation and your browser configuration is the same? Means it's in Roaming.
Local: this data will not be synchronized between machines when you roam. This could be your browser's cache.
Has anyone tried this, any software who has the path hardcoded?
I know for certain that some Adobe products did have these paths hardocded (past tense, haven't tried this now), because I moved my home/user directory on D:, yet they persisted to save the settings in C:\Users.
And half the time you'll find it in the registry too. Linux has proven quite well that an OS doesn't need a registry.
Oh, and what's with ProgramData and AppData being two completely different things. I understand the difference between the two directories, but there is no difference between a program and an app. Everywhere else it's Machine/User.
Linux has proven quite well that an OS doesn't need a registry.
Gnomes dconf would like to have a word with you.
It's really interesting how the Gnome people seem to get rid of every useful feature as it might confuse the user or be complex, but on the other hand add this registry-like anti-feature to make the system just as unmanageable as Windows.
Nowadays, yes. Go back 15+ years, the registry was used extesively.
My reasoning as to why, Linux was never a targeted platform for software back then, now it is. There was only GTK back then and it didn't look "nice" (appealing) at all. Plus GTK apps were huge for Windows, since you'd have to also install the GTK runtimes and all that... that just took a lot of disk space, which was expensive back then. Compared to an app that does the same, but spends only 10% of the disk space needed for GTK (you could even go a lot lower with compressors), it's obvious why GTK was never a viable option when making a GUI app.
And since Linux doesn't have a registry (or even if it did, it'll probably be completely optional to have it or not, so you can't rely on users having it installed), you'd have to just save the settings in a file, just like the rest of the FOSS applications. So, it makes no sense to have completely different codebases for the same app for Windows and everything else. In fact, most apps nowadays that aim to be cross platform just use Qt. You can compile it for watever you like, there is no need to keep separate codebases.
ProgramData is for admin stuff and things that need to be shared between users. AppData is for personalized settings per user. For example, AnyDesk stores the unattended access password in ProgramData, as well as the ID. Sure they do get copied to AppData when AnyDesk runs on boot/login on any user, but you could also have some user specific options (like language) and they get stored in a separate file in AppData.
there is no difference between a program and an app
Yeah the naming is confusing. The reason is what you said - machine vs app.
Back on Windows 9x, some apps would store files directly in the C:\Program Files directory. This was 'fine' at the time since every app ran with full permissions. Users were at C:\Windows\Users, but users were optional so not every install used it.
Windows XP had a better NT-based permission model (not nearly as improved as Vista, but better than 9x) and allowing regular users to write to the Program Files and Windows folders wasn't really a good idea. It added two directories for settings:
C:\Documents and Settings\username\Application Data for user-specific data
C:\Documents and Settings\All Users\Application Data for non-user-specific data
Vista kept the former but moved the latter to C:\ProgramData. I can't remember why.
Linux is confusing for non IT people looking for program settings. It might be in share, local or config or hidden somewhere. On W 10 I just look under ProgramData. Maybe W11 is different. But Linux application devs need to agree on a single place. As users sometimes need to access it for plugins and resources.
You mean the 2 ProgramData folders? Altho who the hell puts config stuff there? Anyways, the 2 official settings apps, the 3 AppData folders and then the registry for every little thing Microsoft doesn't want you to edit for whatever reason? And then the countless 3rd party config apps for every device aiming to make this process easier? Yea I totally don't Google where to toggle stuff on windows as step #1, noo... And W11 just has a slightly better 2nd official settings app, so sadly not too different.
Also who the hell puts config stuff on Linux into /local or /share? It was always in ~/.config (personal) or /etc (system wide) from my experience.
Some people have diacritics and spaces in their usernames, which wreaks havoc for badly written programs accessing AppData or folders in the user's "home" directory, such as Documents. And there are lots of such programs.
When setting up Windows, use a short and memorable, DOS-compatible username, and then change it later (the home folder will still have the old name). You can then move indiidual Libraries (Documents, Downloads, Music, Pictures and Videos) to the root of D:\ too.
Oh no, I think AoE (some version) will sometimes save game file to Documents, and IIRC, wechat will save temp file to documents without user interaction
All that depends on developer. Majority of my used Windows software is portable stored in folder that's synced with Dropbox. All settings are then usually stored in the same folder so I can easily copy SW over to another machine without loosing any configuration / history.
Some of those programs still do not store settings in same folder, you can often simply export settings from GUI.
Most configs should be in the roaming directory, since you'd usually expect them to roam between computers on a domain. The local directory is only for stuff that doesn't make sense to sync to other computers - things like caches, configs specific to that individual PC, etc.
Not that it matters for home users, as home users generally aren't using Active Directory with roaming profiles.