settings schemas & config structure #12

I can think of three tiers of settings * deployment settings -- the main stuff you're thinking about if you're reading this. hosting shit on laptops and trashservers. * user environments -- there's some overlap with deployment settings, but this mostly represents standalone configs a la home-manager. * user preferences -- usually complex settings. For example, plasma-manager et al are good for applying specific declarative settings, but it comes at the cost of being able to use the plasma settings app. Again, there's some overlap with user environments. The line here is a question of UX, controlling a setting with nix locks it down, some deployments might choose not to allow user preferences for this exact reason. Many applications (like my gfs gaming pc), actually really need to be managed using a familiar built-in UI.