>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.
>>107824513sometimes the design violates the user
