@renzev to Programmer [email protected]English • 8 days agoAI's take on XMLimagemessage-square146arrow-up11.23Karrow-down123cross-posted to: programmerhumor
arrow-up11.21Karrow-down1imageAI's take on XML@renzev to Programmer [email protected]English • 8 days agomessage-square146cross-posted to: programmerhumor
minus-square@Gremourlink1•8 days agoYAML for human-written files, JSON for back-to-front and protobuf for back-to-back. XML is an abomination.
minus-square@renzevOPlink2•8 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_manlinkDeutsch1•7 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.