Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] XML not ideal for Big Data

From: Uche Ogbuji <uche@------.--->
To: "Simon St.Laurent" <simonstl@--------.--->
Date: 9/3/2009 5:34:00 PM
On Thu, Sep 3, 2009 at 10:09 AM, Simon St.Laurent <simonstl@s...>wrote:

> Uche Ogbuji wrote:
>
>> I read this, and I decided not to comment, because there is not much nice
>> to say.
>>
>> Goddess knows XML has its problems but in effect this guys is saying "I
>> designed an XML app using XML in a very dumb way, and the app disappointed
>> me.  The fault must lie with XML".
>>
>> Almost every point he touches on is one that I've spent a decade advising
>> clients to deal with successfully.
>>
>
> Fair enough, but this was in 2000 - when I think the XML hype was at its
> height.  I mostly pointed to it as lessons learned, though by some more than
> others!
>

Yeah, fair enough in turn.


I wouldn't say that the fault lies with XML - but I'd happily say that the
> fault lies with common practices around XML, practices that I still hear
> regularly in conversations about how people would like to handle their data.
>

Amen.


 Bottom line: use XML where it's best suited, and employ good XML and
>> systems design.  I know.  Obvious, right?  :)
>>
>
> In 2009, to people who know a fair amount about XML - yes.  To the rest of
> the world - I'm not so sure!
>

Yeah, I should know, having lived through the backlash among Pythonistas,
and having worked hard to strike the right balance, e.g.:

http://www.xml.com/pub/a/2005/08/24/py-xml.html


-- 
Uche Ogbuji                       http://uche.ogbuji.net
Founding Partner, Zepheira        http://zepheira.com
Linked-in profile: http://www.linkedin.com/in/ucheogbuji
Articles: http://uche.ogbuji.net/tech/publications/
Friendfeed: http://friendfeed.com/uche
Twitter: http://twitter.com/uogbuji
Join me at Balisage:
* http://www.balisage.net/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent