5 ms·

Please be civil :). Avoiding ad hominem attacks is more conducive to discussion. I have already justified my preference for jsonfeed. XML has proved many times

Please be civil :). Avoiding ad hominem attacks is more conducive to discussion. I have already justified my preference for jsonfeed. XML has proved many times to decrease developer productivity. To my knowledge open source projects that have dropped or diminished their use of XML have only become more popular over time. Extrapolating a little bit, switching to JSON can only be a good thing.

grzm 8y ago
A key difference now compared to the early days of XML and RSS is there weren't great libraries out there to handle the processing, both output and input. Many people were rolling their own. That definitely wasn't great. It was similar to using JavaScript prior to the widespread adoption of JQuery. However, that's not the case anymore. I think there are possibly a lot of benefits to recommend jsonfeed over RSS (or, a better solution, in my opinion, Atom), but you can build yourself a bit of a straw man by ascribing the problems of early XML usage with the situation today.
bhaak 8y ago
I'm the first person to acknowledge unnecessary use of XML. Historically, XML is infinitely better than the custom formats we had before, where might even have been in binary instead of textual (the horror). Of course they went overboard with XML (oh hello XSLT). But RSS feeds are a prime example for a good use of XML. Standard, validated, machine-parsable, and easily extendable data structures. For example podcast feeds are just extended RSS feeds. I don't think that projects got popular because they dropped XML but because they dropped unnecessary baggage.
elago 8y ago
What is your justification? You already know JSON and you don't wanna learn another notation? You know XML but the use of "<>" are too offensive? If you're such a hacker why not just write a script for yourself that convert javascript to xml instead of making a new standard and fracturing things even more :P Or would you care to share a hack you've done with jsonfeed that I can't do with my RSS reader?

grzm 8y ago

A key difference now compared to the early days of XML and RSS is there weren't great libraries out there to handle the processing, both output and input. Many people were rolling their own. That definitely wasn't great. It was similar to using JavaScript prior to the widespread adoption of JQuery. However, that's not the case anymore. I think there are possibly a lot of benefits to recommend jsonfeed over RSS (or, a better solution, in my opinion, Atom), but you can build yourself a bit of a straw man by ascribing the problems of early XML usage with the situation today.

bhaak 8y ago

I'm the first person to acknowledge unnecessary use of XML. Historically, XML is infinitely better than the custom formats we had before, where might even have been in binary instead of textual (the horror). Of course they went overboard with XML (oh hello XSLT). But RSS feeds are a prime example for a good use of XML. Standard, validated, machine-parsable, and easily extendable data structures. For example podcast feeds are just extended RSS feeds. I don't think that projects got popular because they dropped XML but because they dropped unnecessary baggage.

elago 8y ago

What is your justification? You already know JSON and you don't wanna learn another notation? You know XML but the use of "<>" are too offensive? If you're such a hacker why not just write a script for yourself that convert javascript to xml instead of making a new standard and fracturing things even more :P Or would you care to share a hack you've done with jsonfeed that I can't do with my RSS reader?