tl;dr: I don't know. That's why evening after evening I go on the internet and hope somebody smarter than me will solve humanity's problems. Reflecting on my r

tl;dr: I don't know. That's why evening after evening I go on the internet and hope somebody smarter than me will solve humanity's problems. Reflecting on my remarks, I think I had large configurations in mind as they occur in kubernetes or terraform which can be tens of pages. > How can that be too verbose? I meant that yaml indentations eat up screen space, every attribute needs to go on a new line and is terminated by a colon, which seems redundant since the newline already delimits attributes. If you ever have written a large k8s deployment descriptor, you'll know that yaml is not the right language for describing complex configurations. > How do you suggest specifying a variable? Variables should probably be set outside the template, eg. reference environment variables or be set in INI or properties files... which makes them parameters rather than variables but potato potato. The template could then reference variables by a special notation eg. $myvar or following a naming convention eg. vMyVar. > how do you suggest I differentiate a generated image from a named one? I worded that poorly. I think parsers get too hang up on the details. '"`’«» etc could be all syntactic equals, unless a good use case justifies different meanings. Eg. bash has different meanings for different types of quotes. The parser probably could infer when a statement is a literal vs. a reference simply by checking if the reference exists. > Thank you for your feedback. If you put the specification for your configuration language on a git repo then interested parties could open issues and discuss specific topics.