If somehow you haven’t read the canon of YAML haters (among which I count myself), you gotta check out The YAML Document from Hell. It’ll make you seethe with holy rage.
i get semantic whitespace in python, it makes it less scary for beginners and i personally find it objectively easier to read.
But for config files (which afaik is the whole point of yaml) the parens don't even get in the way, they're actively helpful to find where a section of the config starts and ends! aurgh
Its more like someone picking toki pona for a protocol, which everyone hates and tries to work around without vulnerabilities and other jank, and then the w3c introducing a worse toki pona based on english
God I hate YAML.
If somehow you haven’t read the canon of YAML haters (among which I count myself), you gotta check out The YAML Document from Hell. It’ll make you seethe with holy rage.
Almost all of those issues are solved by quoting the string values.
Oddly it does not even mention the biggest sin and problem with YAML: semantic whitespace.
i get semantic whitespace in python, it makes it less scary for beginners and i personally find it objectively easier to read.
But for config files (which afaik is the whole point of yaml) the parens don't even get in the way, they're actively helpful to find where a section of the config starts and ends! aurgh
This is every yaml document
Thanks for the name idea. Version 1 of the GIHY spec will be out tomorrow.
The spec should just be identical to JSON
But with comments this time
and optional trailing commas.
All my homies hate YAML
wat
Imagine everyone using Latin to program
Someone comes along and says we’re using Jenglish now
Its more like someone picking toki pona for a protocol, which everyone hates and tries to work around without vulnerabilities and other jank, and then the w3c introducing a worse toki pona based on english
we really didn't need the 15th standard
Say Norway to YAML
who asked for this
See also: hjson