>If a 'properly designed yaml schema' was sufficiently powerful for all these use-cases then why does everyone and their third cousin come up with new configuration languages every week?
Coz they fucked up/didn't fix their schema designs and people keep trying to work around that?
I thought I was being very explicitly obvious about this.
Programming is a history of bad designs being worked around with awkward hacks. This is nothing new.
Re:Write Gitlab CI Pipelines in Python Code
by infogulch on Friday April 30, 2021 @03:52PM
(#26998446)
Ah so your argument is that they just aren't doing it right, that a true yaml schema designer wouldn't make this mistake. It's just a mistake.. which keeps being made over and over by everyone that does configuration. Sounds like a no-true-scotsman and "it's the children who are wrong" to me. Can you give any examples of a popular correctly designed yaml schema?
I'm saying that a schema designers reaction to their users using jinja2 or dhall on their YAML ought to be to fix their schema so it's not necessary.
There are plenty of properly designed YAML schemas where people never feel the need to use something like dhall or jinja2.
These arguments aren't holding any water.