@coolbean @phnt @vic the problem with XML is that it makes sense within the SGML lineage which is not how most people experienced it.
SGML was this massive gigaspec where the culture developed a self awareness that you kind of cherry pick which parts fit your budget. it had a lot of human aids to make ex. writing recipes easier. but because it was a gigaspec, and not everyone implements all of it, they decided what if we removed a lot of the customization and just made a dialect with a lot of fixed decisions that people could implement as an exchange format.
that format is XML.
the correct use of XML per greybeards is in the middle of conversion tools. like i posted last year, its like this:
- my cool key checking daemon only supports a single hardened XML parser for configs
- some domain specific language gets used to actually configure it or a GUI
- a translator turns the cool human version in to the XML document, after processing out all of the aids in to a single verbose document that is plainly (if tediously) understood
Sun didn't follow instructions and everyone else met XML through Sun. Thus begins the generational trauma to reinvent XML-but-Worse (JSON) or XML-but-cute (KDL)