Almost all of those issues are solved by explicitly quoting your strings, the author even acknowledges that. Yeah it's annoying that yaml lets you do otherwise, but the title is a bit dramatic.

[–] droans@lemmy.world 1 points 6 hours ago

Or by configuring your parser.

I do agree there are plenty of annoyances that shouldn't exist in YAML but do because someone had an opinionated belief at one point, though. For example, it shouldn't try to guess that "yes", "no", "y", and "n" are truthy values. Let the programmer handle that. If they write true/false, then go ahead and consider those truthy. Times can also be a bit of a pain - iirc writing 12:00 is supposed to be interpreted as 0.5 - but at least that's something you can work around.

But there's plenty in that article that are only problems because the writer made them problems. Every language lets you make mistakes, markup languages aren't any different. It's not a bad thing that you can write strings without quotes. It's not forcing you to do so. Anchors also make it simple to reuse YAML and they're completely optional. The issue with numbers (1.2 stays as 1.2 while 1.2.3 becomes "1.2.3" is very nitpicky. It's completely reasonable for it to try to treat numbers as numbers where it can. If type conversion is that big of an issue for you, then I really doubt you know what you're doing.

On top of all this, YAML is just a superset of JSON. You can literally just paste JSON into your YAML file and it'll process it just fine.

I'm not saying it's perfect, but if you want something that's easy to read and write, even for people who aren't techy, YAML is probably the best option.

[–] Appoxo@lemmy.dbzer0.com 3 points 1 day ago

Coming from powershell scripting, every string is put in quotes and to be printed strings with variables are put in $($var) (e.g. Write-Host "Example-Issue: $($IssueVariable)")
Saves me the trouble of hoping that $($IssueVariable) isnt interpreted as a string by PowerShell.