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
18 Comments
theunknownmuncher@lemmy.world · 22 pts · 178d
God I hate YAML.
lmr0x61@lemmy.ml · 34 pts · 178d
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.
rtxn@lemmy.world · 11 pts · 178d
Almost all of those issues are solved by quoting the string values.
theunknownmuncher@lemmy.world · 13 pts · 178d
Oddly it does not even mention the biggest sin and problem with YAML: semantic whitespace.
Swedneck@discuss.tchncs.de · 6 pts · 178d
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
lastunusedusername2@sh.itjust.works · 7 pts · 178d
This is every yaml document
Sv443@sh.itjust.works · 12 pts · 178d
Thanks for the name idea. Version 1 of the GIHY spec will be out tomorrow.
theunknownmuncher@lemmy.world · 8 pts · 178d
The spec should just be identical to JSON
lastunusedusername2@sh.itjust.works · 7 pts · 178d
But with comments this time
anton@lemmy.blahaj.zone · 2 pts · 176d
and optional trailing commas.
lmr0x61@lemmy.ml · 12 pts · 178d
All my homies hate YAML
QuinnyCoded@sh.itjust.works · 11 pts · 178d
wat
xkbx@startrek.website · 12 pts · 178d
Imagine everyone using Latin to program
Someone comes along and says we’re using Jenglish now
irelephant@lemmy.dbzer0.com · 3 pts · 178d
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
renzhexiangjiao@piefed.blahaj.zone · 10 pts · 178d
we really didn't need the 15th standard
zea_64@lemmy.blahaj.zone · 10 pts · 178d
Say Norway to YAML
Fitzsimmons@lemmy.blahaj.zone · 8 pts · 178d
who asked for this
als@lemmy.blahaj.zone · 1 pts · 178d
See also: hjson