• DavidCameron - Monday, July 21, 2003 1:02 AM

    This article assumes that XML is the way of the future, which is a false assumption.XML has some significant problems.1. Performance. I'm not talking about file size (and the resulting poor performance over networks), but about that fact that parsing XML is an intensive process. For one thing, you must read the entire data structure into memory because you must read to the closing tag. CSV has no such problems.2. Interoperability. XML only works with new stuff and something that can parse XML. Sure it crosses platforms, but you'll find that CSV as a format is even more accepted.Even one of the co-authors of the XML 1.0 standard has pointed out some problems with XML.Seehttp://slashdot.org/article.pl?sid=03/03/18/0712248&mode=thread&tid=95&tid=156That is not to say that XML doesn't have its place. Its place is in small applications that don't deal with much data, and/or have complicated data structures that need to be represented with XML.My impression is that XML is touted as the wave of the future by an increasingly small number of people these days.

    BWAAAA-HAAAA-HAAAAA!!! 😉  I know you're probably not listening anymore but, one visit to this site and, oh my, what a prediction you made 14 years ago.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)