![]() Even worse would be suggesting the use of the registry. There really is no need to directly depend on any Windows API stuff. "Program reads configuration from a file" seems like a really basic thing that every operating system supports. > The specific functionality being used does not 'work just fine everywhere'. Personally I have my system configured so that all "hidden" files are shown because I hate the concept of hidden anything. As far as Linux is concerned they're just normal files on the file system. It's POSIX and GNU programs that choose not show anything that starts with a dot by default. In what reality is someone developing software and building Docker containers who doesn't understand the concept of hidden files? Seems awfully contrived. It turns out that Windows Explorer which doesn't hide dotfiles is much better for developing projects with Docker! But as dotfiles are hidden in Linux you don't see this file and cannot open it. >Imagine if you have a project and want to edit an. If a user doesn't know what a dotfile is they shouldn't have administrative privileges, and if they do get them there is no safeguard to stop them destroying the system. If it is possible for a regular user to accidentally brick a system like this, it was doomed to begin with. You want to delete it as it is empty but accidentally delete important system files. >For example the folder might look empty but in fact it could contain thousands of hidden files. bash_history are, and it can hurt them to accidentally delete or modify them, why show them by default? It's like training wheels on a bike. >What's the point of hiding some of the files in a directory from user? It only makes things more confusing. The worst irony is Microsoft software creating dot-files and dot-dirs on Windows. Instead, it and NTFS have something that's arguably better: a hidden file attribute `FILE_ATTRIBUTE_HIDDEN`, that's again settable/gettable when a file/directory is created or polled, rather than regex-ing for a full-stop. ![]() Windows also doesn't know what the dot at the beginning of a file/folder means. Windows has `%APPDATA%` and `%LOCALAPPDATA%` that are accessible with `ShGetKnownFolderPath`, using the appropriate `KNOWNFOLDERID` all programs should put their configuration and cache data in these paths. What I personally find more egregious are dotfiles and dot-dirs on Windows, created by half-baked ports of Unix-first software (such as `ssh`).
0 Comments
Leave a Reply. |