We need turing completeness in the strangest of places. We can often limit these places to a smaller part of the code. But it's really hard to know beforehand w

We need turing completeness in the strangest of places. We can often limit these places to a smaller part of the code. But it's really hard to know beforehand where those places will occur. Whenever we think we have found a clear separation we invent a config language. And then we realize that we need scripting so we invent a templating language. Then everybody looses their minds and invents 5 more config languages that surely will make us not need the templating language. Let's just call it code and use clever types to separate turing and non-turing completeness?