[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Python and JSON vs XML???

• To: XML Developers List <xml-dev@l...>
• Subject: Re: Python and JSON vs XML???
• From: Michael Champion <michaelc.champion@g...>
• Date: Thu, 25 Aug 2005 10:27:34 -0700
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tQt9GoOPm7r/m6TtBPlpe0RSl3GyZGff+P3yJe42SjPUue2RrHEiwcF++miaUBSBSNUwB4DiiY287AFsrQs68d3Xe3SJUBcp5bzWYLG4bBN0U2KqPIc1tFhu40XdzoWpvRxZB6w8AjrLnxc168UoyKABlAfqgGKYr8ekAV8+A3Q=
• In-reply-to: <001b01c5a97e$713131b0$a300a8c0@RW>
• References: <e3a5cb2c05082500045293f51e@m...> <001b01c5a97e$713131b0$a300a8c0@RW>

On 8/25/05, Pete Cordell <petexmldev@t...> wrote:

> Whether the observations made below represent a genuine move away from XML,
> or represent a small pocket of newly discovered dissenters I don't know.

Neither do I, that's why I'm asking.   If these are fragmented domains
in which XML just isn't needed, I don't think XML stakeholders need to
think too hard about how to react to or accomodate JSON.  Nobody ever
said that XML was good for everything, just that its network effect
makes it good enough for a lot of things.  If the native tools in a
specific environment are more suitable for things like config files
and quickn-n-dirty client/server protocols, I can't think of too many
reasons to suggest XML over than JSON, Python syntax stuff, etc.. 
Once you start having to talk across platforms, however, you start
getting benefits in return for the XML tax.

Sorry for the unintended slur against XSLT's utility as a "programming
language".  Obviously some people can indeed work wonders with it, and
maybe more people should learn to do so.  My point is simply that
languages and DSLs that use XML syntax get a lot of resistance from
users, and that cases like XSLT where the XML syntax actually improves
that language for typical use cases are rare.  Does anyone disagree
with that?

Thanks to the various  people reminding me of YAML ... it was produced
by a spinoff of a spinoff of xml-dev so I should have made the
connection!  It hasn't exactly disrupted XML after 5 years or so now,
but I suppose that it could ride Ruby's coattails to hypedom.

As much as part of me would enjoy the show if something like JSON or
YAML disrupts XML from below (in the original Clayton Christensen
sense of providing a simpler/cheaper technology that is good enough
for the typical user of the previous generation and hence kills demand
for the previous generation), I'm extremely skeptical that it will
happen.  Few people really have to confront the complexity in the
specs or the ugliness where the various XML technologies rub against
one another.  The alternatives make life a lot easier for geeks but
it's not clear to me whether they do anything to help the Pointy
Haired Bosses of the world.  Of course, neither did PCs, the internet,
XML, dynamic languages, etc. a few years before they took off, but
they offered a LOT of benefit at a MUCH lower cost than the previous
generation of stuff did.  I don't see that order of magnitude
difference between XML and JSON, (or binary XML for that matter),
hence my skepticism.

• Follow-Ups:
  • Re: Python and JSON vs XML???
    • From: Alan Gutierrez <alan-xml-dev@e...>

• References:
  • Python and JSON vs XML???
    • From: Michael Champion <michaelc.champion@g...>
  • Re: Python and JSON vs XML???
    • From: "Pete Cordell" <petexmldev@t...>

• Prev by Date: Re: Python and JSON vs XML???
• Next by Date: Re: Python and JSON vs XML???
• Previous by thread: Re: Python and JSON vs XML???
• Next by thread: Re: Python and JSON vs XML???
• Index(es):
  • Date
  • Thread