In some cases they are. Global config needed to support a local module(As in a PHP app depending on proper Apache conf) kinda sucks because it can create confl

In some cases they are. Global config needed to support a local module(As in a PHP app depending on proper Apache conf) kinda sucks because it can create conflicts that can only be solved manually or with a container. Settings that can't be done via GUI suck. I shouldn't have to dig through some other app and copy and paste an IP address to use your thing. Settings should not have to change for common activities. US vs Metric should be a document property. I should not have to change settings to properly view a certain document. Settings without sane defaults suck too. A good setting is "Here's a discovery server, but you can change it". A crappy setting is "Select an API version for this global daemon that 5 other things use, and only 3 can work at the same time". Anything that can by dynamic and autodetected... probably should be unless there's a really good reason.