4 ms·

No, "self-documenting" is not what I would ~/.config. At best you have to Google till you find random documentation like [1] and manually go and edit the file.

No, "self-documenting" is not what I would ~/.config. At best you have to Google till you find random documentation like [1] and manually go and edit the file. At that point I fail to see how that's any easier than downloading the .reg file right there and just double-clicking it. Moreover, if you insist on doing it the hard way, it's just a matter of copy-pasting the path in 2022 (not 1995)'s regedit and then right-click -> New -> Value. Still just as easy (arguably easier) than modifying a text file. And Microsoft documents a lot of keys too, just not everything. Not like Linux is exactly known for fantastic documentation either. [1] https://wiki.archlinux.org/title/font_configuration#Anti-aliasing https://wiki.archlinux.org/title/font_configuration#Anti-ali...

ubercow13 5y ago
I dunno, I think that's reasonably well-documented without needing Google: https://linux.die.net/man/5/fonts-conf https://linux.die.net/man/5/fonts-conf.
- dataflow 5y ago
  To me the Arch docs for this are about 10x better than that man page, and neither of them is discoverable for the average user without Google. And double-clicking a file is surely easier to me than editing one. We have a very different sense of good and bad.
infamia 5y ago
I've spent a lot of time in both the registry and config files. The big advantage of config files over the registry is you get encapsulation for free with config files. With the registry the system, apps, hardware, etc. are free to (and do) spew their config entries across the universe. Searching for a magic registry key in HKLM or HKCU is a special kind of awful I don't care to revisit.
- dataflow 5y ago
  "Encapsulation" might be a bit of an overstatement for a model where programs instead spew out their stuff into ~/.myapprc, ~/.config, ~/.cache, ~/myapp, ~/.local, /opt/share, /etc, /var, dconf, gconf, ...
  - infamia 5y ago
    When I said encapsulation, I just meant that all the settings are in one file, vs. spread out amongst keys all over HKCU which is often the case in the registry.

ubercow13 5y ago

I dunno, I think that's reasonably well-documented without needing Google: https://linux.die.net/man/5/fonts-conf https://linux.die.net/man/5/fonts-conf.

dataflow 5y ago
To me the Arch docs for this are about 10x better than that man page, and neither of them is discoverable for the average user without Google. And double-clicking a file is surely easier to me than editing one. We have a very different sense of good and bad.

infamia 5y ago

I've spent a lot of time in both the registry and config files. The big advantage of config files over the registry is you get encapsulation for free with config files. With the registry the system, apps, hardware, etc. are free to (and do) spew their config entries across the universe. Searching for a magic registry key in HKLM or HKCU is a special kind of awful I don't care to revisit.

dataflow 5y ago
"Encapsulation" might be a bit of an overstatement for a model where programs instead spew out their stuff into ~/.myapprc, ~/.config, ~/.cache, ~/myapp, ~/.local, /opt/share, /etc, /var, dconf, gconf, ...
- infamia 5y ago
  When I said encapsulation, I just meant that all the settings are in one file, vs. spread out amongst keys all over HKCU which is often the case in the registry.