Statically typed schema eliminate the ambiguity and so you get to have your legibility cake and eat your consistence cake too.
Statically typed schema eliminate the ambiguity and so you get to have your legibility cake and eat your consistence cake too.
But inevitably, in order to DRY, somebody will make a consistent parser that is used in your application, whether that's in-house or a dependency. And at that point, it is very tempting to run everything through the parser, and the parser is going to make some unexpected decisions.
So, sure, use INI. But don't really. Use a env file that is parseable as INI or as shell environment variables. As soon as you start needing anything more complex, use something where you have at least a few basic guarantees that what you're getting is at least in the general vicinity of what you want.
If you haven't checked it out, NestedText takes this approach.