Re:To Facebook the answer must be no
by axod on Wednesday April 21, 2010 @08:08PM
(#1283623)
One of the whole points about JSON is that you can write a serializer/deserializer in a few lines of code. It's a ridiculously simple, standard format.
Compare that with massive bloated complex XML parsers.
Re:To Facebook the answer must be no
by abstractbill on Wednesday April 21, 2010 @08:30PM
(#1283669)
And an even better thing is that you almost never have to - the list of languages without a free standard implementation of json is pretty uninteresting.
I like json a lot - it's a better reincarnation of s-expressions than xml was. The only thing I wish for is that it had a symbol type, so that I could use it as a syntax for programming languages as well as data ;)
Re:To Facebook the answer must be no
by natrius on Wednesday April 21, 2010 @09:54PM
(#1283852)
"One of the whole points about JSON is that you can write a serializer/deserializer in a few lines of code."
Not without a good library for parsing. I'd be impressed by a robust JSON parser written in a few lines of code using just the standard library of any language.
Look at that data and tell me it's beautiful and efficient. It's a crapfest of mammoth proportions.
Unfortunately in the case of youtube, you can ask for it in JSON, but it'll just take the crapfest of XML and convert it to an even bigger pile of rubbish:
Re:To Facebook the answer must be no
by veemjeem on Wednesday April 21, 2010 @11:38PM
(#1284055)
I don't know if there should be standards for json objects. JSON always reminded me of duck-typed objects whereas XML reminded me of strongly-typed (via the DTD) objects.
Re:To Facebook the answer must be no
by cookiecaper on Thursday April 22, 2010 @03:41AM
(#1284422)
I syndicated his blog for the better part of a year and found most of his posts to be misguided. I think you're right that he just doesn't like it when things change.
Re:To Facebook the answer must be no
by hristov on Wednesday April 21, 2010 @09:28PM
(#1283784)
"Facebook is to be the identity system for the web. A company? That just can't work. I can't believe he doesn't know that. Even Bill Gates didn't have the audacity to propose that!"
Re:To Facebook the answer must be no
by programnature on Wednesday April 21, 2010 @08:55PM
(#1283716)
I can't decide what is more comical. That he's going to write off FB and Twitter because parsing JSON is too hard. Or that he thought the Open Graph was a bad idea in 1997 and still thinks so today, and apparently is proud of it. Or that he thinks FB could buy Microsoft.
Re:To Facebook the answer must be no
by jonknee on Wednesday April 21, 2010 @08:29PM
(#1283664)
It must be frustrating to develop when you have to look at everything through a two decade old lens. Dave has had some brilliant ideas, but sticking with a hacked together dead environment is making him irrelevant.
Re:To Facebook the answer must be no
by abstractbill on Wednesday April 21, 2010 @08:48PM
(#1283703)
It must be frustrating to develop when you have to look at everything through a two decade old lens.
You don't have to though. I've seen a lot of stuff reinvented already, some of it badly. That doesn't stop me from doing the pragmatic thing most of the time though.
Re:To Facebook the answer must be no
by loup-vaillant on Thursday April 22, 2010 @04:16AM
(#1284463)
I hoped to see a political argument, and instead saw a technical, unimportant one.
Because I agree with the title: Facebook promoting unnecessary centralization and large scale spying, the answer must be no. We just need a decentralized replacement, so it can be no.
Compare that with massive bloated complex XML parsers.
Good on them for using JSON.
I like json a lot - it's a better reincarnation of s-expressions than xml was. The only thing I wish for is that it had a symbol type, so that I could use it as a syntax for programming languages as well as data ;)
Not without a good library for parsing. I'd be impressed by a robust JSON parser written in a few lines of code using just the standard library of any language.
JSON on the other hand, means you have to write your own parser.
And really, why not do as twitter does and make it available in both xml and json formats?
http://gdata.youtube.com/feeds/api/videos/cK3N2DC3Fds
Look at that data and tell me it's beautiful and efficient. It's a crapfest of mammoth proportions.
Unfortunately in the case of youtube, you can ask for it in JSON, but it'll just take the crapfest of XML and convert it to an even bigger pile of rubbish:
http://gdata.youtube.com/feeds/api/videos/cK3N2DC3Fds?alt=js...
Its 2009 man, grow up Dave. XML lost.
But yeah, json is becoming the syndication format.... Are there standards for json objects yet?
RSS ⊂ XML
http://techcrunch.com/2005/08/21/dave-winers-creates-a-purpl...
The dude invented RSS, but still. Old dog, new trick?
Is it just me or does this read like an old out-of-date guy that doesn't like change?
My personal experience is that JSON is very easy and getting OAuth signatures right is like stabbing yourself in the eyes with hot needles.
Dude, you don't remember Passport?
You don't have to though. I've seen a lot of stuff reinvented already, some of it badly. That doesn't stop me from doing the pragmatic thing most of the time though.
I did not realize that in 2010 any mainstream environments did not have a JSON library!
I only ask because I haven't seen one, at least not one that is built in and guaranteed to work.
Because I agree with the title: Facebook promoting unnecessary centralization and large scale spying, the answer must be no. We just need a decentralized replacement, so it can be no.