3 ms·
The issue with XML is that it was mostly pushed upon developers without any deeper understanding. So there's a ton of utterly crap XML applications out there w
by dragontamer 6y ago
The issue with XML is that it was mostly pushed upon developers without any deeper understanding.
So there's a ton of utterly crap XML applications out there with no rhyme or reason, and these crap XML enterprise apps are most developer's understanding of "real world XML". Similar to how terrible C++ code being all over the place is making people hate C++ the language.
-------
XML can be used very well however: its use in Jabber / XMPP is clear and concise. XML Namespaces are needed due to the extensions of XMPP, and various programs can interact with the protocol. Specifications are clear, the ability to "stream" data is proven, different parser strategies have been implemented. Its clear that XML in this instance works, and works pretty well.
- vollmond 6y agoAround 2009, I worked on an application whose web interface and API were the same url -- it was served as an XML data file, with an XSLT transform to make it pretty for the browser. It was so comfortable.
- eska 6y agoI really like the separation between the semantic content and the visualization there. HTML/JS/CSS throw everything together instead. But XSLT is nothing I want to have to work with..
- duxup 6y ago>crap XML enterprise apps are most developer's understanding of "real world XML" I mean if there's enough of it, it kinda becomes "real world XML". Right or wrong human's ability to actually use the tool or tech well is often where the bar is set. Could be a great idea but if folks can't do it... won't fly.
- commandlinefan 6y ago> without any deeper understanding I can't count how often I've seen XML that looked like this: <container name="containerName"> <attribute name="attrib1" value="value1" /> <attribute name="attrib2" value="value2" /> <attribute name="listAttibute" value="pipe|delimited|values" /> <attribute name="containedAttribute" value="<container name="otherContainer"..." /> ... </container> Which was, technically, XML (it even conformed to a schema!)... almost like "malicious compliance".