renzev@lemmy.world to Programmer Humor@lemmy.mlEnglish · 8 months agoAI's take on XMLlemmy.worldexternal-linkmessage-square129fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-linkAI's take on XMLlemmy.worldrenzev@lemmy.world to Programmer Humor@lemmy.mlEnglish · 8 months agomessage-square129fedilink
minus-squareGremour@lemmy.worldlinkfedilinkarrow-up0·8 months agoYAML for human-written files, JSON for back-to-front and protobuf for back-to-back. XML is an abomination.
minus-squarerenzev@lemmy.worldOPlinkfedilinkarrow-up0·8 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
minus-squareit_depends_man@lemmy.worldlinkfedilinkDeutscharrow-up0·8 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.
YAML for human-written files, JSON for back-to-front and protobuf for back-to-back. XML is an abomination.
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
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.