← Back to context

Comment by Y-bar

6 hours ago

We stopped having this problem over ten years ago when spec 1.1 was implemented. Why are people still harking on about it?

9 comments

Y-bar

Reply
merelysounds  2 hours ago

A new spec version doesn’t mean we stop having the problem.

E.g. kubernetes wrote about solving this only five months ago[1] and by moving from yaml to kyaml, a yaml subset.

[1]: https://kubernetes.io/blog/2025/07/28/kubernetes-v1-34-sneak...

  • Y-bar  2 hours ago

    The 1.1 spec was released about _twenty_ years ago, I explicitly used the word _implemented_ for a reason. As in: Our Yaml lib vendor had begun officially supporting that version more than ten years ago.

Etheryte  5 hours ago

Because there's a metric ton of software out there that was built once upon a time and then that bit was never updated. I've seen this issue out in the wild across more industries than I can count.

  • Y-bar  2 hours ago

    I’m not here clanking down on Java for lacking Lambda features, the problem is that I did not update my Java environment past the 2014 version, not a problem with Java.

    • Etheryte  1 hour ago

      I think this mixes up two separate things. If you're working with Java, it's conceivable that you could probably update with some effort. If you're an aerospace engineer using software that was certified decades ago for an exorbitant amount of money, it's never going to happen. Swap for nearly any industry of your liking, since most of the world runs on legacy software by definition. A very large number of people running into issues like these are not in a position where they could solve the problem even if they wanted to.

actionfromafar  6 hours ago

Now add brackets and end-tags, I'll reconsider. ;)

  • Y-bar  5 hours ago

    Brackets works fine:

        Roles: [editor, product_manager]

    End tags, that I’m not sure what that is. But three dashes is part of the spec to delineate sections:

        something:
        setting: true
    ---
    another:
        thing: false

quotemstr  4 hours ago

Because once a technology develops a reputation for having a problem it's practically impossible to rehabilitate it.