I’ve seen XML parsers that will convert element content from strings to native types by default. So “0” becomes an int, “true” becomes a boolean, and “null” becomes an actual null. I had to take extra steps to keep everything as a string unless explicitly told not to.
I’ve seen XML parsers that will convert element content from strings to native types by default. So “0” becomes an int, “true” becomes a boolean, and “null” becomes an actual null. I had to take extra steps to keep everything as a string unless explicitly told not to.
JSON does not have this problem, BTW.
I don’t think anyone actually chooses XML. There’s no reason to use it over JSON unless you need to.
Really? Right in front of my AJAX?
The entirety of the banking world uses XML very heavily, as it’s part of the SWIFT standards.
I didn’t say that it’s not used. I say that you shouldn’t if you have the option.
If the entire X world uses Y technology. You have no choice other than using Y technology.