1. There is not a single YAML format. Different parsers support varying formats and specs.
2. YAML is a terrible format for everyone. Even if you don't hate it, you can still fall prey to its poor design and not even know about it until it blows up later. A package manager is especially not somewhere you want such latent bugs.
3. Not everybody knows its terrible quirks. I'd used YAML for years, and was still surprised when I read strictyaml.org's (limited) list of documented bugs in YAML.
4. YAML isn't even the first or most-popular well-known format. So, if you're going to advocate for a well-known format that everybody can use, it makes little sense to advocate for YAML.
Yes YAML is a terrible choice, but his point is still correct. Use a standard format, not some custom nonsense you made up that can't even handle strings with spaces in them.
I recommend JSON5 or maybe TOML if your data is very flat.
> Yes YAML is a terrible choice, but his point is still correct. Use a standard format ...
As I said in point 4 above: So, if you're going to advocate for a well-known format that everybody can use, it makes little sense to advocate for YAML.
2. YAML is a terrible format for everyone. Even if you don't hate it, you can still fall prey to its poor design and not even know about it until it blows up later. A package manager is especially not somewhere you want such latent bugs.
3. Not everybody knows its terrible quirks. I'd used YAML for years, and was still surprised when I read strictyaml.org's (limited) list of documented bugs in YAML.
4. YAML isn't even the first or most-popular well-known format. So, if you're going to advocate for a well-known format that everybody can use, it makes little sense to advocate for YAML.