• LordKitsuna@lemmy.world
    link
    fedilink
    arrow-up
    81
    arrow-down
    8
    ·
    20 hours ago

    Anyone that says yaml is readable is psychotic. It’s literally objectively not readable because a random white space character can break the entire thing and that’s by definition not readable I can’t see whether there’s a white space or not without explicitly setting that up in an editor

      • azertyfun
        link
        fedilink
        arrow-up
        9
        arrow-down
        1
        ·
        16 hours ago

        Only 1.1. Which everybody has been fiercely clinging onto since 2009, because YAML 1.2 did not seem to consider it a problem that they broke backwards compatibility on that behavior. So now the only way to keep existing YAML files working is for us all to keep pretending YAML 1.2 does not exist.

          • azertyfun
            link
            fedilink
            arrow-up
            1
            ·
            7 hours ago

            Which versioning???

            somekey: yes
            

            Go right ahead and tell me what the YAML version is and what is the type of somekey is. Oh that’s right, it’s impossible, because the versioning is entirely up to the serializers for some godforsaken reason.

        • corsicanguppy@lemmy.ca
          link
          fedilink
          English
          arrow-up
          1
          ·
          10 hours ago

          they broke backwards compatibility

          Tell me this is post-y2k and built in the dark ages after we lost our mentors and gurus without using those words.

      • LordKitsuna@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        15 hours ago

        I mean sure or you could just start by using a format that’s not so painfully strict with how it’s laid out. I miss the good old INI config. It couldn’t give two shits how you format it, throw in random spaces random tabs random new lines so long as the value was correct