Friday April 29th

Thursday April 28th

Wednesday April 27th

Why XML SUCKS

As many of my colleagues know, I am not a really big fan of XML. I think it's bloated. I think it's not needed. I don't think it accomplishes much if anything that couldn't be done before just by sending text delimited in a different way. I'm not sure why if I want to tell someone a yes or a no answer on something being found, I have to wrap it in 1000 characters of SOAP data when i could just send a 0 a 1 or nothing and accomplish the same thing. Or why if I want a list of data, I have to wrap it up and package it as XML when I could just send the list as regular delimited text instead of delimited by 20% text bloat of so-called self description. Anyway, that's the short version of why I think XML sucks. Here are some other people that think it sucks and some much more in depth articles about it. =)

8 comments

Sorry, but no kick from me. The link takes you to the paragraph above plus links to other, more thoughtfully written XML-related articles by other authors on other sites.

Really bad article, ½ blogspam. First of all, none of his "arguments" stick.

"'I' m not sure why if I want to tell someone a yes or a no answer on something being found, I have to wrap it in 1000 characters of SOAP data when i could just send a 0 a 1 or nothing and accomplish the same thing'm not sure why if I want to tell someone a yes or a no answer on something being found, I have to wrap it in 1000 characters of SOAP data when i could just send a 0 a 1 or nothing and accomplish the same thing"

Well, hello, who says you have to do that? <answer>none</answer>. Most of the links on his "post", are to really bad articles, with really bad "solutions". (i love the cleartext-solution on http://c2.com/cgi/wiki?XmlIsJustDumbText - "How do you express collections and hierarchical data").

XML is great, as long as you know how to use it. If royashbrook only can return true/false on a request using 100 characters, i am pretty sure he should stay away from it. If not for himself, then for us!

No kick from me either.

There are many times when XML may be overkill, returning an article kick count at JSON or even a single integer certainly makes sense. I would be interested in seeing an implementation of the various WS-* specifications without using a rich data representation language like XML though.

Lets take a shot at: http://www.artima.com/intv/plain4.html

"XML sucks because it's being used wrongly" That has to be one of the, most used, bad arguments ever. It should be "some users of xml suck".

I can understand their arguments about ant-files, but how should it be done otherwise? No solution aint better than a working one. If someone found it hard to edit ant-files, he could have said "Oh look, here's an XML parser.", and created a tool to edit them.

This is why DotNetKicks need to have some kind of Bury feature, so we can -1 kick this for sucking.

Agreed....how did this suddenly make it onto the front page with 9 kicks after being lost in the "upcoming stories" section for *days* with only 2 kicks?

As with any other tool, XML has its uses. Is it always the right tool for the task? No way. But that doesn't mean that there are not legitimate uses for XML.

No kick from me.

Commenting on Stories is limited for now and will open up to those recommended by the community. Learn how
Loading DotNetKicks...
brought to you by the Kicks Network