ZZartin (4/11/2016)

---

Jeff Moden (4/10/2016)

---

Heh... ok... I take it back. I was asked to troubleshoot some problems in some code I've never seen before and I now even hate XML used for configuration settings. There's nothing to ensure that a tag hasn't been duplicated or misspelled and it takes just as much brew-ha-ha to extract the settings from the XML as it does an EAV table. The XML is also a hell of a lot more difficult for a human to read than the return from an EAV. I see no justification nor any advantage for such a thing.

This seems like kind of a symptom of application developers just wanting an easy to parse thing and for that XML works great in theory in their dev environment. Then it hits a production setting and you have a huge XML config file.... and have fun....