I don't think that's necessarily a bad thing. In a lot of situations a plain yaml file is good enough for templating, and people seem to prefer writing those ov

I don't think that's necessarily a bad thing. In a lot of situations a plain yaml file is good enough for templating, and people seem to prefer writing those over json, for several reasons. Then, there are a lot of situations where templating yaml files is good enough. So, I do think having tools to do that sorta thing is good. With more complex system like for example Kubernetes those solutions start to not be good enough any ore, which is why things like jsonette are being adopted. And sooner later 'real' languages. Which, evemtually, will help develop abstractions that have a simple enough interface so we are able to use plain key value pairs for config again. And so on. I guess the point I'm trying to make is that it's not black and white, and a lot of the solutions that appear in this space have a good reason to exist. Well, obviously, since someone took the time to solve a problem they thought was not solved well enough with existing tools.