XML is better than YAML

Re:XML is better than YAML by emodendroket on Thursday September 21, 2023 @01:49PM (#37601296)

If that exact same configuration were JSON or XML would it be easy to sort out? It seems obvious to me that it wouldn’t because the configuration itself is complex.

[ Parent | on HN ]

Re:XML is better than YAML by pjmlp on Thursday September 21, 2023 @06:36PM (#37605404)

XML definitely, as it is structured, with schema validation.

[ Parent | on HN ]

Re:XML is better than YAML by emodendroket on Thursday September 21, 2023 @07:01PM (#37605621)

Structure and schema validation are not typically something your VC cares about since it treats everything as text. So I'm not seeing why that resolves the problem.

[ Parent | on HN ]

Re:XML is better than YAML by boredtofears on Thursday September 21, 2023 @09:21PM (#37606721)

Because it doesn't make it to your VC in the first place if it doesn't pass schema validation.

[ Parent | on HN ]

Re:XML is better than YAML by emodendroket on Friday September 22, 2023 @12:01AM (#37607688)

Except you were just talking about "merge conflicts..." two valid versions of the configuration don't necessarily stay valid when they get merged together.

[ Parent | on HN ]

Re:XML is better than YAML by pjmlp on Friday September 22, 2023 @03:45AM (#37609130)

Because a savy developer will validate their schema when sorting out merge conflicts across the whole configuration, instead of commiting a badly merged file that will fail starting up the Kubernetes cluster in the sea of YAML files.

[ Parent | on HN ]