Comment by praptak

Yes! Everyone thinking of a new config language should look at jsonnet first. And there are much bigger reasons (than just syntactic stuff) hidden in the "interesting things" part.

The "interesting things" include being (or at least aiming to be) the solution to the following problem:

"I need to configure ~200 tasks for each of 7 services in 5 datacenters where some stuff is dependent on DC, some on (service+DC) combination and also some machines where the jobs run need per-machine config overrides.

I want to avoid manual copy-paste-modify and I want to avoid the hell of generating configs from a Turing-complete language"