Check the book _Coders at Work_ by Peter Seibel. There's a chapter
interviewing Douglas Crockford, inventor of JSON, created for the very
reasons you mention. Douglas is a proponent of simple(r) solutions.

"Crockford: [...] Like when XML was proposed as a data-interchange format,
my first impression of that was, 'My god, this is way, way, way too
complicated. We don't need all of this stuff just to move data back and
forth.' And so I proposed another way to do it, and it won. JSON is now the
preferred way of doing data transfer in Ajax applications and it's winning
in a whole lot of other applications. And it's just really simple." pp. 125

--Loyd

On Mon, Dec 28, 2009 at 7:21 AM, Aaron Bartell <aaronbartell@xxxxxxxxx>wrote:

JSON is more quickly parsed/composed on the client than XML because of it's
nativeness to Javascript. Really, in the end, JSON is a great alternative
to XML for more than just communicating with a browser because of it's
simplicity and yet still maintaining the main things you need in XML (i.e.
tagged data, groups of data, repeating data, basic data types).



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.