Not at all, actually it is much better than JSON or YAML, which its advocates eventually had to come up with all the tooling that XML already had in place.
Schemas, comments, transformation tooling, IDE integration,....
Schemas, comments, transformation tooling, IDE integration,....
How many Kubernetes administration headaches trace back to the need for automated systems to surgically edit YAML? It’s absurd and YAML may be the worst choice for this use case.
Kubernetes makes me miss WebSphere 5, the version is on purpose, before the usability goodies that came up in 6.1.