>program files x86>program files x64>users/user/appdata/local>users/user/appdata/locallow>users/user/appdata/roaming>users/user/appdata/roaming/programs>users/local/>programdata (hidden)>/my saved games>/my documents/saves>/my documents/game/saves>/my documents/company/game/saves>://winstoreapps>setting not stored anywhere but written into the registry
shitnux is even worse
>/user/.program
>>107824448God damn you're right. None of those are adequate and all this is just going to confuse our users. Going forward, let's settle on a new system. Maybe a hidden c:/allappdata for all all data except saved games and config files because those belong in a non hidden c:/user/all/app/data.
>system32 (contains 64bit libraries)>syswow64 (contains 32bit libraries)
>>107824610wow64 stands for "windows (32 bit) on windows 64 bit" so it makes sense for it to contain 32bit libs
>>107824488This is one of those things you're just wrong about, as many flaws as it has configuration portability is without exageration 20 years ahead of windows on loonixOh wait I forgot when you're not retarded with computers you run everything on windows in virtual machines and containers becuase otherwise the OS is just so unbearable to use, this solves the issue entirely
>system drive: C:>why not A: or B:? cuz floppy disks were A: 40 years ago
>>107824448>~/.local/.config>~/.config/config>~/.config/program/config>/usr/local/config>/usr/share/config>/etc/config.d/config>/etc/program/config>~/.program/config>~/var/config>~/opt/program/config
>inetpub>it cannot be deleted>it cannot be hidden
>>107824448Appdata is a good standard
>>107825277>~/.local/.config>~/.config/config>~/.config/program/configthese are ok>/etc/program/configthis is ok for stock configs and system-level application configurationdon't forget>~/For shell configs and stuff which is fine in my book. Better than fish with its gay directory structure.everything else is gay
>>107825266Backwards compatibility. Just like most of the quirks mentioned in this thread
>>107824448Honestly, global filesystem views are retarded. Should have different layers. Global, user and application desu.
>>107824448Don't forget C:\inetpub because M$ updates can be used to hack you if that folder doesn't exist.
>>107825277>>~/.local/.config>>~/.config/program/config>>/usr/local/config>>/usr/share/config>>~/var/configmeds>>~/opt/program/config>>/etc/config.d/config>>/etc/program/config>>~/.config/configthese are real, and ok>>~/.program/configin this situation you're supposed to find the author's minecraft server and lay TNT blocks under the floor boards
>>107825284Blame M$ jeets for making that the default home folder for IIS. It should have been something like C:\ProgramData\IIS or whatever. Also the fact that the root drive had an ACL (by default) that allows all users to add whatever directory they want and Windows updates running as root and iis specific changes can be tricked into executing arbitrary code.
>greasy drama queen>mumbles in native English >actually makes effort when speaking Chinese
>>107827100>~/.program/configthere's a workaround for this mental illness#!/bin/shexec bwrap --dev-bind / / --bind ~/.local/share/sandbox/program ~ program "$@"
#!/bin/shexec bwrap --dev-bind / / --bind ~/.local/share/sandbox/program ~ program "$@"
>>107824645What? Who thought of that? Thats retarded
>>107824448never understood this shitIf im not demented everything was going under program files or windows before
>>107827132he's so babygirl...
>>107825277The only acceptable way is to keep all xdg-compliant configurations in /etc/ or ~/.config/,placing all non-compliant configs in ~/.config/, as well, unless it's simply not an option, and keeping a directory in your ~/ where you cp -r all of your edited dotfiles and cp -rs the directories back in place. Then, root can take custody of the configuration files with trusted code.
>>107827232No it's not.Windows was widely regarded as a 16-bit DOS app. So they called the compatibility layer "Windows on Win32", shortened to WOW32.Fast forward 15 years, Windows was widely regarded as a 32-bit environment. So they called the compatibility layer "Windows on Win64", or WOW64.You need a System folder for the files used by the compatibility layer, and you might as well name it after the compatibility layer, so "System Folder for Windows on Win64", or SysWOW64.
>>107824448I see you like playing with big toys.
>>107824448yep i hate itso I just use portable things. Doesn't stop registry use though I think
>>107827052interesting
>>107824448>>107824488Kek unironically these days yeah, Linux has the same problem.
>>107825266>>why not A: or B:?But in Japan A: was the hard drive.
>>107824448>>107825277sbin bin usrbin usrsbin usaarbinwhy every os do this
>>107832615because someone's computer ran out of space like 40 years ago.I am not joking
>>107824448>>>setting not stored anywhere but written into the registryFuck Izotope, what were they thinking with this?
>>107825277Gobal vs user scope, also some of those don't exist.
>>107832725a shitload of software (especially audio software) are obsessed with using the system registry for everything and insisting on installing most of the data into a home folder when you specifically set a directory for the plugin.
>>107830757>>107830805>7 hours
>>107832615Legacy junk. On modern Gentoo, /bin, /sbin, and /usr/sbin are all just symlinks to /usr/bin.
>>107830805Hot
>>107825190>>107824488>/etc/>/var/lib/>~/.config/>~/.local/state/>~/.var/app/that's just off the top of my head
>>107824448I just realized appdata means "app data", I've going into that folder for at least 10 years just thinking "what a funny name"
Can someone please explain to me what the advantage of using the windows registry over a database or even a normal json config file is? It just makes the program platform dependent.
Why the fuck are portable programs not the standard....
>>107825190>you run everything on windows in virtual machines and containersIs this opposite day or something? Do you not realize what flatpak, snap, and docker are? What about appimage?99.9999% of all windows programs are installed directly onto the OS and run natively whereas the situation on Linux is so flaky that every single "modern" program packaging format is just bundling a micro OS or building your program into a container.
>>107824448at least for the most part (in my experience), applications do respect the appdata/local and appdata/roaming conventions. You can usually copy appdata/roaming if needing a quick and dirty migration of a user to another computer and get most of the important stuff.>>107833549I am by no means a windows expert, but I do have some experience in the registry. It was a genuinely pretty brilliant idea that just never had great execution. I think it would have been adopted better if it had a more intuitive interface.>users and computer has it's own hive files that are automatically loaded.>in theory, user's registry would store all of their application customizations and could be copied between computers.>very easy to export keys and re-import them (natively in the shell). Easy to back up.The problems arise that it was conceived at a time when the assumption was that users either were always admins, OR that users would NOT be able to install their own software. Which was pretty naive, hence all the hacks that devs do to bypass the HKLM and C:\Program Files.
