3 ms·

Sure. http://boston.conman.org/index.atom http://boston.conman.org/index.json http://boston.conman.org/bostondiaries.rss Each one contains the ful

• oliwarner 8y ago
  Thank you for sharing that. It took me a little while before I noticed it, but your JSON files have more data. Each item has a id, date_published and tags field which do not feature in the RSS. Together these account for around 250chars per item or 3750chars per 15 item feed. Cut out those fields and the JSON would be 850chars shorter. Also, you're preserving tab and newline characters around HTML. This affects JSON more because a newline is valid between RSS tags. In JSON a newline becomes two characters "\n", as a tab becomes "\t". Going "spaceless" on output would save you 1372chars from your JSON feed (and half as much from RSS/ATOM). I will confess, my sniff test didn't account for using quite as many HTML attributes as you do :) Escaping double-quotes costs you 334 in JSON. The overall difference is much slighter than I had expected.