1486
DF General Discussion / Re: Future of the Fortress: List of Remaining Items
« on: March 01, 2010, 02:30:23 am »so your example of support is someone using it? the differences between the two are moot for the purposes of DF. in a nutshell xml is a robust version of html, and json is a stripped down version of java. since json is leaner than xml it can run faster, however since it uses java as its primary tool it won't run faster in the long run. if that changes then it will run faster in the long run, but that is a big if. now since we are using it for exporting information, which is done on a computer rather than over the net we don't have to worry about bandwith issues, or how well a tool can process the stuff inside of an open browser, nor how it affects other pages/tabs. once that stuff is removed the only functional difference is that json reads closer to that of text, which is what it is now, thus changing it to something that reads worse (xml or json) is a step backwards. you have the same info in the document, thus converting is trivial, and since converting a document rarely takes a noticeable amount of time when being run right before some sort of application it becomes pointless what format is used in regards of app compatibility other than whether or not the information is there. in the end text is slightly better than json, which is slightly better than xml, at least for our purposes (and thus text is the clear winner since it is already in that format).if someone comes along and supports json then it will be the new hotness, until then it is just for the pie in the sky dreamers, in reality there is no serious functional difference between the two.
There's lots of support for it. MIT's Simile uses JSON for its data, and all the nerds who love Drupal seem to think JSON is sweet like a Jaguar XKE (Try breeding one of those...).
Spoiler (click to show/hide)