I'm not against something similar to the INI file format, especially as someone raised on MS-DOS 6.22. However, you're getting dangerously close to suggesting something akin to the Windows...
I'm not against something similar to the INI file format, especially as someone raised on MS-DOS 6.22.
However, you're getting dangerously close to suggesting something akin to the Windows Registry, and honestly it's not a terrible idea (a central repository of settings, not the actual regedit).
I too agree that the "dot files" are basically a giant mess, but then again that's Linux: it's messy, and rarely is a unified systematic approach applied. I think systemd is the only modern ideology I can think of that brought order to chaos, but not without a lot of anger along the way (and perhaps still).
"Hidden files" are a bug, that was kept around for reasons nobody would even consider implementing if it was first suggested today - the reason they became popular was because they could make...
I too agree that the "dot files" are basically a giant mess
"Hidden files" are a bug, that was kept around for reasons nobody would even consider implementing if it was first suggested today - the reason they became popular was because they could make $HOME look clean instead of having to clutter up the directory with lots of config files, and the bug inadvertently created a whole new category of files that was kept just for this one feature.
I sort of disagree, mostly because every OS does this. For example, macOS with .DS_Store files, and Windows with it's Hidden flag and Thumbs.db, Desktop.ini, $RECYCLE.BIN, etc. I think there's a...
I sort of disagree, mostly because every OS does this. For example, macOS with .DS_Store files, and Windows with it's Hidden flag and Thumbs.db, Desktop.ini, $RECYCLE.BIN, etc.
I think there's a reason every OS sort of went down this path, and while above I suggested a centralized settings repo like the registry, it can't solve everything.
So I guess my question to you: what alternative do you envision to the dot file mess on every OS? If they started over today, what do you think they'd adopt as a better system?
There is only really one solution to this for me: Use nix with home-manager and generate all of your configuration files and never think about where they live again.
There is only really one solution to this for me: Use nix with home-manager and generate all of your configuration files and never think about where they live again.
I really think linux would benefit from a different home structure. Something like /users/$USER/home/ instead of /home/$USER/. Let anyone pollute /users/$USER/ however they want, but I’d rather...
I really think linux would benefit from a different home structure.
Something like /users/$USER/home/ instead of /home/$USER/. Let anyone pollute /users/$USER/ however they want, but I’d rather not have files not created by me existing in my /~.
Something that I miss from when I used Windows Managers is the possibility of having all of your desktop tweaks in one single file or folder. I would love if Desktop Environments started to bundle...
Something that I miss from when I used Windows Managers is the possibility of having all of your desktop tweaks in one single file or folder. I would love if Desktop Environments started to bundle core configuration files and interface-related user preferences in a single file or folder that would allow for backups or version control.
And I'm over here just wishing I could have a clean home directory! You can make absolutely whatever mess you want in ~/.config. I'll be thrilled to see the mess contained to a single directory.
And I'm over here just wishing I could have a clean home directory! You can make absolutely whatever mess you want in ~/.config. I'll be thrilled to see the mess contained to a single directory.
I am one of those weirdos, and I am happy and appeased with the standardization of the .config folder (though sadly not everyone uses the standard). I still fully agree with you. I have no problem...
I am one of those weirdos, and I am happy and appeased with the standardization of the .config folder (though sadly not everyone uses the standard).
I still fully agree with you. I have no problem with chaos within ~/.config.
IMO the problem with those articles is that the author wants to avoid this chaos, not realizing it is unavoidable.
In truth, at some level there will be chaos, you cannot avoid it, so we just standardize it and move on. Im not sure if further complexity in the standard adds or reduces utility value.
Furthermore, the simplicity/ease of using single per-app config files is hard to beat and much better than things like universal system/app registries etc.
Dont fix whats not broken is the engineering motto, right?
I can only assume that the people that care about this sort of thing are spending more time ricing their OS than they are actually using it to accomplish literally anything else you can use a...
I am a loss to explain to anyone why this article exists.
I can only assume that the people that care about this sort of thing are spending more time ricing their OS than they are actually using it to accomplish literally anything else you can use a computer for. Nobody needs to look at (or even be aware of) the contents of ~/.config/ to play games, record music, edit video, browse the web, or type a document.
If you have managed dotfiles for multiple systems it can matter. Just because some folks don’t see a problem with a junk drawer doesn’t mean we can’t talk about ways to organize things. The...
If you have managed dotfiles for multiple systems it can matter.
Just because some folks don’t see a problem with a junk drawer doesn’t mean we can’t talk about ways to organize things.
The responses in this thread are making some pretty big assumptions. You don’t care, fine, but that doesn’t mean the folks who do aren't doing anything but making things look a certain way.
I'm not against something similar to the INI file format, especially as someone raised on MS-DOS 6.22.
However, you're getting dangerously close to suggesting something akin to the Windows Registry, and honestly it's not a terrible idea (a central repository of settings, not the actual
regedit).I too agree that the "dot files" are basically a giant mess, but then again that's Linux: it's messy, and rarely is a unified systematic approach applied. I think
systemdis the only modern ideology I can think of that brought order to chaos, but not without a lot of anger along the way (and perhaps still)."Hidden files" are a bug, that was kept around for reasons nobody would even consider implementing if it was first suggested today - the reason they became popular was because they could make $HOME look clean instead of having to clutter up the directory with lots of config files, and the bug inadvertently created a whole new category of files that was kept just for this one feature.
I sort of disagree, mostly because every OS does this. For example, macOS with
.DS_Storefiles, and Windows with it'sHiddenflag andThumbs.db,Desktop.ini,$RECYCLE.BIN, etc.I think there's a reason every OS sort of went down this path, and while above I suggested a centralized settings repo like the registry, it can't solve everything.
So I guess my question to you: what alternative do you envision to the dot file mess on every OS? If they started over today, what do you think they'd adopt as a better system?
There is only really one solution to this for me: Use
nixwithhome-managerand generate all of your configuration files and never think about where they live again.I really think linux would benefit from a different home structure.
Something like
/users/$USER/home/instead of/home/$USER/. Let anyone pollute/users/$USER/however they want, but I’d rather not have files not created by me existing in my/~.Kind of like
C:\Users\$USER\AppData? :)Exactly what I was thinking :)
Something that I miss from when I used Windows Managers is the possibility of having all of your desktop tweaks in one single file or folder. I would love if Desktop Environments started to bundle core configuration files and interface-related user preferences in a single file or folder that would allow for backups or version control.
And I'm over here just wishing I could have a clean home directory! You can make absolutely whatever mess you want in ~/.config. I'll be thrilled to see the mess contained to a single directory.
I am one of those weirdos, and I am happy and appeased with the standardization of the .config folder (though sadly not everyone uses the standard).
I still fully agree with you. I have no problem with chaos within ~/.config.
IMO the problem with those articles is that the author wants to avoid this chaos, not realizing it is unavoidable.
In truth, at some level there will be chaos, you cannot avoid it, so we just standardize it and move on. Im not sure if further complexity in the standard adds or reduces utility value.
Furthermore, the simplicity/ease of using single per-app config files is hard to beat and much better than things like universal system/app registries etc.
Dont fix whats not broken is the engineering motto, right?
I can only assume that the people that care about this sort of thing are spending more time ricing their OS than they are actually using it to accomplish literally anything else you can use a computer for. Nobody needs to look at (or even be aware of) the contents of
~/.config/to play games, record music, edit video, browse the web, or type a document.If you have managed dotfiles for multiple systems it can matter.
Just because some folks don’t see a problem with a junk drawer doesn’t mean we can’t talk about ways to organize things.
The responses in this thread are making some pretty big assumptions. You don’t care, fine, but that doesn’t mean the folks who do aren't doing anything but making things look a certain way.