2 ms·
JSON is easier to parse if you have to write your parser from scratch, but there are parsers for nearly all languages so you don't have to. JSON on the other h
by tomjen3 17y ago
JSON is easier to parse if you have to write your parser from scratch, but there are parsers for nearly all languages so you don't have to.
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?
- axod 17y agoHere's for why. http://gdata.youtube.com/feeds/api/videos/cK3N2DC3Fds 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=json http://gdata.youtube.com/feeds/api/videos/cK3N2DC3Fds?alt=js...
- tomjen3 17y agoIt is not beautiful, but when I throw my LINQ-to-xml magic at it, it will be quite easy to work with.