renzev@lemmy.world to Programmer Humor@lemmy.mlEnglish · 2 months agoAI's take on XMLlemmy.worldimagemessage-square131fedilinkarrow-up11.25Karrow-down123cross-posted to: programmerhumor@lemmy.world
arrow-up11.23Karrow-down1imageAI's take on XMLlemmy.worldrenzev@lemmy.world to Programmer Humor@lemmy.mlEnglish · 2 months agomessage-square131fedilinkcross-posted to: programmerhumor@lemmy.world
minus-squareGremour@lemmy.worldlinkfedilinkarrow-up3arrow-down2·2 months agoYAML for human-written files, JSON for back-to-front and protobuf for back-to-back. XML is an abomination.
minus-squareit_depends_man@lemmy.worldlinkfedilinkDeutscharrow-up2·2 months agoHaving an easy on the eyes markdown that is also easy to parse would be cool. But YAML does these things: https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell which are not excusable, for any reason.
minus-squarerenzev@lemmy.worldOPlinkfedilinkarrow-up2·2 months agoYAML is good for files that have a very flexible structure or need to define a series of steps. Like github workflows or docker-compose files. For traditional config files with a more or less fixed structure, TOML is better I think
YAML for human-written files, JSON for back-to-front and protobuf for back-to-back. XML is an abomination.
Having an easy on the eyes markdown that is also easy to parse would be cool.
But YAML does these things:
https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell
which are not excusable, for any reason.
YAML is good for files that have a very flexible structure or need to define a series of steps. Like github workflows or docker-compose files. For traditional config files with a more or less fixed structure, TOML is better I think