quote:

---

My fault on the English - we haven't decided what to do just yet. Clearly if can't follow the article it's of no value, yet we don't have time to rewrite content that comes in from readers who use English as a second language.

Andy

---

quote:

---

My respect for the author writing an article in the first place. Those of us who do it on a regular basis know how hard it can be. It's that much harder when it's not in your native language.

---

very well said!!!

In fact, that's what refrains me from submitting some article yet.

In addition, I'm at war with english punctuation. (to be honest, I'm with german to a certain degree, too )

Let' s look at this as a first try, which is always the hardest one.
And maybe as a suggestion to the SiteOwners, to review articles from non native english speakers before publishing. That means no proofreading or editing, just 'normal' reading.

Cheers,
Frank

quote:

---

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.

---

funny anecdote on this happened yesterday.

I was in a project meeting with our IT staff. Basically to discuss how to get mutual fund quotes into our mainframe.

When it comes to the 'which format' question, I said with your post in mind, hey, let's do it with XML. It's universal, trendy blabla..

Before going on, I must say, I really like our mainframe guys. They are innovative, flexible, open for new thoughts.

Guess what they said!

No, no XML, only CSV, that just fine. We can reuse existing code.. and anyway who cares about XML.

Well!



Cheers,
Frank