A riddle for you then:

A man on a business trip is in Florida and decides to give his wife back home in Oregon an "I love you honey" call. During the conversation he off-handedly mentions the time of day. His wife replies, "Hey, that's the same time that it is here!"

How is that possible?

You think it is actually tidy underneath there?

http://www.nytimes.com/interac...

Any company that has 200 devs working on the same codebase is in trouble. They just don't know it yet.

Every programmer is a trial and error programmer.

The sneer is affectionate because every engineer has sometimes kludged things together.

And they all converge towards LISP.

OMG, it's another sign of global warming!!!

But I am an IBUer!

They are directly competing now that RedBox has a streaming plan.

The Apple Stores sell an external SuperDrive for $79.

Red Box is waaaaaaay cheaper than Netflix and you can get BluRay discs too!

nt

It's entire structure is *derived* from printer tags and most are useless. Apps that don't know what they are sending or receiving shouldn't be doing it in the first place. And in fact they don't. The whole semantic web concept is total BS and is in fact a total failure.

No b2b apps really need it as they are all custom built and the apps cloned from them already know the semantics of the data or they wouldn't have bothered to clone from them in the first place. XML is just added after the fact. It is useless cruft.

Why do you think everyone hates it? It's as bad as C++ which requires full knowledge of the application specific templates to be of any use. Kill them both.

No it is not weird. XML is weird because it contains and is based on printer control cruft. Lots of printer control cruft. An unnecessary tag is a tag is a tag is a fucking tag.

Why do you think everybody hates it? Why do you think there are plans afoot (like the subject of this article) to get by without it?

XML sucks because it is based on a printer control spec. It's as simple and as ugly as that.

Yes. I'm lucky LISP can parse XML since they are really only just a special case of S-Expressions. Once out of that horrid mess of printer tags it was much more straightforward to validate them and insert them in all their complexity into a nicely normalized relational database.