That's a Lot of YAML

Yaml is the language nobody needed. All we wanted was a better JSON format that supports comments and doesn’t crash with an extra comma as the end of a list, eg: [1,2,3,]

This format is unreadable on mobile, it keeps opening up my keyboard and scrolling up a bit when it does.<p>I understand and appreciate the &quot;why&quot; of the format, but this also could have been a non-editable &quot;editor-like&quot; presentation and achieved the same result.

Yeah theres some problem, but reading a multiline code block (like github actions bash script) as an indent-escaped string is so much better than having to understand crazy triple-escaped characters like &quot;sed \&quot;\\\\\\&quot;name1\\\\\\\&quot;\&quot;&quot;

I will die on the hill that TOML should be used for the vast majority of what YAML&#x27;s used for today. There are times a full language is needed, but I&#x27;ve seen so many YAML files that use none of the features YAML has with all of the footguns.

I find the configuration complexity clock always valuable in framing conversations like this: <a href="https:&#x2F;&#x2F;mikehadlow.blogspot.com&#x2F;2012&#x2F;05&#x2F;configuration-complexity-clock.html?m=1" rel="nofollow">https:&#x2F;&#x2F;mikehadlow.blogspot.com&#x2F;2012&#x2F;05&#x2F;configuration-comple...</a>

I&#x27;m a big fan of YAML after coming from JSON and, later, ProtoBuf&#x27;s many definition formats while working at Google---but it&#x27;s true that there are a lot of oddities in YAML&#x27;s magical parsing. I&#x27;m grateful for the many ways it&#x27;s possible to quickly an naturally define simple hierarchies of data (for example, in a docker-compose file).<p>This website does the rare thing of, after complaining, providing a long list of alternatives. It&#x27;s really nice.

YAML&#x27;s idea of human readability misses the mark. Especially anchors. They&#x27;re the worst tools for abstraction.<p>JSON with functions as the high level format and JSON as the low level format is the way to go. Examples include Nix and Jsonnet. They&#x27;re much nicer to deal with and less error prone.

&gt; # Anyone wondering why their first seven Kubernetes clusters deploy just fine, and the eighth fails?<p>Yay, octal numbers! But don&#x27;t panic, lots of supposed C programmers fall for exactly the same trick when prefixing numbers with `0`.

I can take credit for one of these, the 63 ways to wrap a string, on line 156.

All I see is Lisp:<p>#Operator: - Operand 1 - Operand 2

When it comes to AWS Cloudformation, I love YAML. Can&#x27;t think of any other positive use though.

I like writing yaml<p>(context: I&#x27;ve never had to write 1000-line yaml files for kubernetes)

Yawn. I&#x27;ll keep using XML. While many waste their youth pointlessly reinventing XSDs in YAML&#x2F;JSON&#x2F;TOML&#x2F;JSON5&#x2F;HJSON, I&#x27;ll still be here. Living. Content.