JSON vs. XML

[Verahta]

This came up in another thread and I thought it might deserve it's own thread. What are your own opinions on JSON vs XML? He is probably biased, but the 'creator' of JSON explains in this short interview why it's better than XML (at least in his opinion, though he does give tangible reasons).

Discovering JavaScript Object Notation with Douglas Crockford
https://www.youtube.com/watch?v=kc8BAR7SHJI

[Jackolantern]

JSON is, for the most part, a better choice. It is more readable and compact. Plus, with the increasing popularity and ubiquity of Javascript, the fact that JS can natively consume JSON data without any library or translation required is quite handy.

For any online game, the compactness of JSON data can end up being a huge bandwidth saving when you look at a whole month at a time.

[Chris]

JSON is very simpe and straight foreward, you cannot define relations to parts of data. XML can be used for small scale (preferably not) to very large complex relational structures.

It's like comparing procedural code with asynchronous. Or comparing classical mechanics with Quantum mechanics.

[Jackolantern]

JSON can represent relations. To my knowledge, XML cannot represent anything that JSON cannot also represent. They are both just different ways of representing data's structure.

[Chris]

JSON can represent relations. To my knowledge, XML cannot represent anything that JSON cannot also represent. They are both just different ways of representing data's structure.

the whole benefit of XML is not only being able to place data withing the tag, but also adding parameters:

Code: Select all

<entity parameter="property value"><secondaryEntity /></entity>

To achieve this with JSON would be rather difficult as you only store lists of data or singularity data.

[kaos78414]

JSON can represent relations. To my knowledge, XML cannot represent anything that JSON cannot also represent. They are both just different ways of representing data's structure.

the whole benefit of XML is not only being able to place data withing the tag, but also adding parameters:

Code: Select all

<entity parameter="property value"><secondaryEntity /></entity>

To achieve this with JSON would be rather difficult as you only store lists of data or singularity data.

Why wouldn't this suffice?

Code: Select all

{ "entity": { "parameter":"property value", "secondaryEntity": { } } }

[Chris]

That could be processed to the same result but it took three objects instead of two. The way I look at it is in two directions. XML can go both, JSON can only go in one.

Like RNA and DNA.

Try developing a Windows 8 App with XAML, you'll come to terms with it.

[Verahta]

http://stackoverflow.com/questions/3536 ... l-and-json

[Jackolantern]

XML is a better fit to me for UI-related work, such as XAML or Android UI. So I will definitely give XML that. Comparable UI systems made with JSON (and there are only a couple I know of) just feel clunky and foreign. I don't know if this actually has anything to do with its abilities, or just that XML feels like HTML.

However, I much prefer JSON for actual data transfer.

[Chris]

"XML is like violence. If it doesn't solve your problem, you're not using enough of it."
- Unknown | Chris Maden

I lol'd