4 ms·
Not sure what all the fuss is about. It's actually neat to have a common way of changing JSON to XML, think of a web service that offers an API using our belove
by wulczer 15y ago
Not sure what all the fuss is about. It's actually neat to have a common way of changing JSON to XML, think of a web service that offers an API using our beloved JSON. But wait, we also want to provide an XML API! Let's design our own, ad-hoc, crappy mapping or... use that thing that everyone else is using.
XML is out there, has lots of tools and libraries and is actually useful for some things. Not to mention the array of technologies around it, like XPath, XQuery etc, that JSON is lacking (probably because it doesn't need it, because these formats do address slightly different requirements. Gasp!).
- Stormbringer 15y ago"the fuss" is because a lot of people jumped on the JSON bandwagon in order to get away from XML.
- wulczer 15y agoThat's fine for them. My question stands: what's wrong with someone proposing a generic way of transforming JSON to XML?
- scott_s 15y agoThen wouldn't it make sense to allow people who are stuck using XML in some places to convert to JSON when talking to those that aren't stuck with XML?
- rbanffy 15y ago> But wait, we also want to provide an XML API! Why would you want to do that? Govt contracts? Purifying your soul through suffering? All I want from my XML APIs is to give error messages telling the user to upgrade to the JSON ones. ;-) > XML is out there, has lots of tools and libraries and is actually useful for some things. A lot of things had to be invented in order to make XML useful.