While conversing with Linux users, they should know what dir means... I mean, even if they don't use the terminal that often, dir is often used in GUIs as well in Linux.
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.
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.
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.
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.
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.
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.
Probably just log in an out, but still, I fail to see how this is easier than changing some_bool_setting from =true to =false is harder... maybe because you actually know what you're changing, so that makes it scarier 🤔.
There are symlinks in Windows all over the place for backwards compatibility. Just look at "Documents and Settings", it's a symlink to ”Users".
Yet, you still have to install the same libraries with every app over and over, even though they can be shared. Why? Because Windows has no sense of default library locations, except for the things it absolutely needs to work.
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.
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.
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.
The real magic word ( sh.itjust.works ) Englisch
2nd hand ThinkPad go brrrrr ( sh.itjust.works ) Englisch
Made me chuckle ( sh.itjust.works ) Englisch
Dual booters be like ( sh.itjust.works ) Englisch
How to pickup girls 101 ( sh.itjust.works ) Englisch
To be honest, it is quite complicated now as well with all of the proprietary software ( sh.itjust.works ) Englisch
/usr/bin/cat ( sh.itjust.works ) Englisch
Man pages bad ( sh.itjust.works ) Englisch
All I wanted to do was just watch pr0n... ( sh.itjust.works ) Englisch
And then you get hooked on it and start using it for real ( sh.itjust.works ) Englisch