Funny, Dave’s post and the subsequent excellent discussion have probably inadvertently pushed JSON’s awareness level a little higher (based on all the positive exclamations of discovery in that thread), more people will end up using JSON now, thanks to Dave’s ignorance.
Hopefully all the thoughtfully written comments have helped Dave learn what JSON is all about. Of course there was some off-the-cuff ranting to add to the comedy. Here’s the rant in case he later takes it down:
IT’S NOT EVEN XML!
As Dr Phil asks — What were they thinking?
No doubt I can write a routine to parse this, but look at how deep they went to re-invent, XML itself wasn’t good enough for them, for some reason (I’d love to hear the reason). Who did this travesty? Let’s find a tree and string them up. Now.
Ladies and gentlemen, boys and girls, this is why I’m fed up with Mountain View, Cupertino, Redwood Shores and Redmond. Give me Berkeley and New York any day. Silicon Valley is made up of little boys pulling their puds, constantly making love to each other, pretending the world revolves around them.
The funny part is that JSON is so much simpler than any other format out there, so I really do find it surprising that Dave doesn’t “get it”. Sometimes it’s hard to tell when someone is just clueless or on an ego trip (and hey, everyone is a little of both once in awhile). Here are some choice nuggets from the comments section:
Spoken like someone who really wants to get something done instead of mess around with XML parsing to extract an array of integers…
Exactly! There was no “pud-pulling” here, Dave.
I liked the part where Dr Phil said “What were they thinking?” I asked the same question when I first saw XML being proposed as a data format. There were obviously better alternatives.
The good thing about reinventing the wheel is that you can get a round one.
Me too Of course, I have learned since those earlier, naive days that XML has its place and certainly isn’t going away anytime in the foreseeable future…