4 ms·
A message from the (now defunct) XML community: "We've gotten to a point where a human-readable, human-editable text format for structured data has become a com
by lolive 9y ago
A message from the (now defunct) XML community:
"We've gotten to a point where a human-readable, human-editable text format for structured data has become a complex nightmare where somebody can safely say "As many threads on xml-dev have shown, text-based processing of XML is hazardous at best" and be perfectly valid in saying it. -- Tom Bradford"
- appleflaxen 9y agoI never used xml. can anyone who used it at a time when it was vogue give a brief overview of "what happened"? I'd love to read it, if you have the time (or point me toward a good summary).
- lolive 9y agoVery basically, XML is a document format. Inherited from SGML. The point of the statement is to say that all the "clever tricks" that XML permits (entities, encoding, well-formedness, validation, ...) make it unsafe to manage by hand. (I.e by appending strings together to build an XML, or by tokenizing a XML input string). From there, you need tools and API to manage your XML representation. And mapping technologies to recreate objects in memory from an XML content. All these (over engineered) tools make things overly complex when you want to exchange documents. And a true nightmare when you exchange data structures. The alternative of JSON and JSON.parse() is extremely lightweight in comparison. JSON is basically Javascript already. And you can create JSON from any in-memory data structure, with any programming language. Today, XML should be used only to exchange structured documents. (Which was its primary goal, btw ;)