2 ms·
I'm surprised no one has mentioned his freakout over JSON, yet (http://www.scripting.com/stories/2010/04/26/theToxicCoralReef.html#p8 http://www.scripting.com/s
by aaronbrethorst 17y ago
I'm surprised no one has mentioned his freakout over JSON, yet (http://www.scripting.com/stories/2010/04/26/theToxicCoralReef.html#p8 http://www.scripting.com/stories/2010/04/26/theToxicCoralRee...). Apparently, Twitter turning off XML output and standardizing on JSON is "even more dramatic" than the Basic Auth-to-OAuth transition.
Frankly, I don't get it. Dave's argument appears to be that because the tooling he uses (Radio Userland?) doesn't support JSON, and therefore he will stop writing tools for Twitter (he wrote Twitter-related tools?).
He's the only person I've ever read who seems to prefer XML to JSON. Is there anyone else out there who feels the same way? What's the perceived advantage of XML over JSON? Can anyone shed some light on this?
- metajack 17y agoI'm not going to defend Winer's point of view, but I also prefer XML for some tasks. Namespaces make XML extensible in a way that JSON is not. In XML, I can add an attribute or a child node anywhere without affecting anything else. There is no easy way to extend JSON without jumping through ugly hoops to recreate a more XML-like data model.