3 ms·
I'm afraid your argument of "It worked for us" and "it only uses a small number of files with 30 custom namespaces" pretty much is the most unconvincing argumen
by moonshinefe 12y ago
I'm afraid your argument of "It worked for us" and "it only uses a small number of files with 30 custom namespaces" pretty much is the most unconvincing argument I've ever heard.
In fact, the latter point is one of the reasons most people like to avoid XML.
- ilitirit 12y agoYeah XML namespaces are a pain to work with, but when it comes to stuff like documentation it's hard to beat XML. Mixed content in Json is definitely not as simple as it is in XML.
- geonik 12y ago"the latter point is one of the reasons most people like to avoid XML" And these are exactly those who will never "get" that XML is much more than a data container for tree-like structures. They should stick to JSON or CSV for that matter.