News for hackers. Stuff that matters.
Re:Configuration files suck. Just use a programming language by dalke on Sunday July 27, 2014 @01:58PM (#8093420)
This is a long debate, with no resolution. Eg, http://taint.org/2011/02/18/001527a.html from 2011 is "Against The Use Of Programming Languages in Configuration Files", with links to resources both pro- and con.

In Python, you see migration away from the Turing-complete "setup.py" configuration language to a special purpose "setup.cfg", in order that dependency systems can reason about the configuration without worrying about the Halting Problem.

Re:Configuration files suck. Just use a programming language by curtis on Sunday July 27, 2014 @03:22PM (#8093686)
I think the problem is the implicit assumption that configuration has to be all the way one way or the other. In my experience you want configuration to be mostly declarative, but you also want to augment that configuration with limited amounts of actual code.
Re:Configuration files suck. Just use a programming language by dalke on Sunday July 27, 2014 @04:25PM (#8093866)
I think it's an explicit assumption. Either a configuration language is Turing complete or it isn't.

I think I know where you're coming from - if you are a human reading the configuration then you can analyze the actual code. But that's only one dimension of the problem, because it requires a human to be in the loop.