Comment by rad_gruchalski
3 years ago
> Because to understand the configuration files, you have to understand the programs they are inteded for and the environments they end up in, and the language they are written in.
Seems like the right approach. To use something, one has to understand how to use it. Why is this unusual?
Your comment makes it sound like my problem with configurations is that they require understanding something.
But that's not what I said.
What I said is:
> Configuration is opaque. Undebuggable. Unmaintainable. By its very nature. No matter what "language" you use for it.
The underlying point - perhaps not metioned explicitly - is that they are way too complex for what you achieve with them.
Of course, complex systems require a deep level of understanding. But everything being equal, complexity is a thing to avoid - when you can do it without loss of capability.