RSS in JSON, for real?

  A short while ago Twitter said they were going to move to JSON over XML, without much explanation other than they like JSON and not XML, so much, these days, etc. I'm a big believer that everyone has the right to support whatever they want when they want for whatver reason, whether they say the truth or not. Because of that belief, I take with a grain of salt every bit of support for every format and protocol. I assume that just because someone supports it today doesn't tell you for sure that they will support it tomorrow. Though the penalty is usually pretty high for removing support for interfaces people depend on. They tend to remember it next time you ask for their trust. All that is fair game too.
  So anyway this got me thinking again about the possibility that JSON might take over from XML. What then? Should we give up all the interop we get from RSS just because it uses XML and not JSON? And it's because of all that interop that that day will never come. A transition may happen over a long period of time, and before it's complete there will be something after JSON. Because smart people see that, they tend to be conservative about switching just for the sake of switching. It's why the web, which is entirely an XML application, will keep XML support everywhere for the forseeable future.
  In other words, I'd bet with virtual 100 percent certainty that it's safe to keep producing XML-based RSS feeds.
  But people like JSON, there's no denying that. And a JSONified RSS can totally co-exist with the original XML. So let's have RSS in JSON? That's a question that seems worth asking about, at this time.
  Turns out it is a very straightforward thing to do. I of course have an RSS feed for Scripting News, the blog you're reading right now. I wrote a script that maintains JSON and JSONP versions of the same content, automatically. When the RSS is built so are the JSON formats.
  http://scripting.com/rss.json and http://scripting.com/rss.js
  I learned a long time ago to embrace change. It's why there is a RSS today that is derived from the RSS that Netscape shipped in 1999 and has features of my scriptingNews format shipped in 1997. If the world wants to go to JSON, help it get there in a way that benefits from all we learned in the evolution of RSS from 1997 through 2002. It's stood up pretty well over the years. And there's wide support for it, and lots of understanding of how it works. If there is to be a JSON-based syndication standard, we can cut years off the development process by simply accomodating it.
  So I put together an invitation to discuss this.
  http://rssjs.org/
  If you find this interesting, give it some thought, and if you have something to say, write a blog post of your own, or write a comment on that page. Obviously there's no moderation for what goes on your blog, but there will be moderation of the comments. Be aware of that. One feature of the past are personal attacks which are totally pointless and subtract from the discourse, and we should not carry that practice forward. That's why the moderation. :-)
  Otherwise, I totally look forward to hearing what people think.
  Thanks...