Thank you for the link. It's a new application so I didn't really mean "new format" so much as what you would like to see the configuration itself support. (May

Thank you for the link. It's a new application so I didn't really mean "new format" so much as what you would like to see the configuration itself support. (Maybe I should have said: "when you find that an application has a configuration file, what are the characteristics of that file in terms of functionality and format that you like to see - what do you like to be able to configure in an application and how do you like to be able to configure it using a configuration file, in terms of both structure and functionality?") You mention "Is it a good idea to still force a single file once the configuration reaches some sufficiently large size?" If it is not limited to a single configuration file what do you suggest is best practice for which one(s) should be loaded?