@[email protected] to Programmer [email protected]English • 8 months agoAI's take on XMLlemmy.worldimagemessage-square135fedilinkarrow-up11.25Kcross-posted to: [email protected]
arrow-up11.25KimageAI's take on XMLlemmy.world@[email protected] to Programmer [email protected]English • 8 months agomessage-square135fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilink3•8 months agoYAML for human-written files, JSON for back-to-front and protobuf for back-to-back. XML is an abomination.
minus-square@[email protected]OPlinkfedilink2•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-square@[email protected]linkfedilinkDeutsch2•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.