A sane program knows were to find the "random" configs: first, in cwd, then $XDG_CONFIG_HOME, then $XDG_CONFIG_DIRS. This is not exactly "obscure", you learn it soon and it's documented in every program.
The big advantage of this is that you can take your local config files and take it to other system. Can you do that with the Windows registry? Ironically, the only way to port settings in Windows is to have a .reg script and execute it, the thing you critisize.
And the Windows registry might be a single centralized config file, but config values are scattered through all the tree, and usually undocumented. E.g. this is a commonly recomended tweak:
The big advantage of this is that you can take your local config files and take it to other system. Can you do that with the Windows registry? Ironically, the only way to port settings in Windows is to have a .reg script and execute it, the thing you critisize.
And the Windows registry might be a single centralized config file, but config values are scattered through all the tree, and usually undocumented. E.g. this is a commonly recomended tweak:
HKEY_CURRENT_USER\Control Panel\Desktop] "UserPreferencesMask"=hex(2):90,12,03,80,10,00,00,00
Can you tell what it does?