@renzev@lemmy.world to Programmer Humor@lemmy.mlEnglish • 11 days agoAI's take on XMLlemmy.worldimagemessage-square135fedilinkarrow-up11.24Karrow-down122cross-posted to: programmerhumor@lemmy.world
arrow-up11.22Karrow-down1imageAI's take on XMLlemmy.world@renzev@lemmy.world to Programmer Humor@lemmy.mlEnglish • 11 days agomessage-square135fedilinkcross-posted to: programmerhumor@lemmy.world
minus-square@Gremour@lemmy.worldlinkfedilink2•11 days agoYAML for human-written files, JSON for back-to-front and protobuf for back-to-back. XML is an abomination.
minus-square@renzev@lemmy.worldOPlinkfedilink2•10 days 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@it_depends_man@lemmy.worldlinkfedilinkDeutsch1•10 days 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.