This was nice to wake up to.
This was nice to wake up to.
I realized that I want my blog to be me on the web. This used to be true, but then along came Twitter, and then my presence got split up between two places.
Welcome back to using one spot to blog and microblog Brent.
I find myself in the same dilemma with Instagram lately. I publish photos there first and sometimes post them here. That will change starting this week. I’m going to try to share photos on my blog first and then maybe go to Instagram. Enough monkeying around!
Manton Reece and Brent Simmons have created a new specification for creating feeds using JSON. They write:
We — Manton Reece and Brent Simmons — have noticed that JSON has become the developers’ choice for APIs, and that developers will often go out of their way to avoid XML. JSON is simpler to read and write, and it’s less prone to bugs.
JSON Feed has been implemented on a few platforms already and it was talked about a lot since its debut. I’m glad someone has created a spec around this so that the developers that would like to use this can now rally behind a unified specification. However, JSON Feed won’t be replacing RSS any time very soon.
RSS is something you could call a “good enough” solution. It is already in place, tons of stuff supports it, and works fine. And while the developers of all of the apps and services that use RSS could update their software to create and parse JSON Feed it is doubtful they will very quickly as the benefits aren’t all that great. The advantage of JSON Feed mostly comes when creating new services not replacing old ones.
I don’t think Manton and Brent believe JSON Feed will replace RSS. I don’t think that is why they created the spec. I believe they feel this is a good alternative for the developers that would like to use it and that they wrote the spec out of a need that they had. Which is good.
I’ve discussed the benefits of replacing RSS with JSON in the past. Me, in June 2015 on one of the benefits of replacing RSS with JSON:
RSS is a fairly bloated specification. It is a bit verbose and the file sizes for even a small blog can get relatively large quickly. JSON is, by its very nature, a bit more succinct. This would result in faster load times, easier caching, etc.
So while there are definite benefits, it is doubtful that RSS is going anywhere for a long time. There have been a few attempts to replace RSS with something that is smaller and easier to parse over the years and they simply didn’t catch on. This weekend Dave Winer (the inventor of RSS) chimed in on JSON Feed and he has a similar reaction to it as I have had; it is great that the specification exists but it will not be replacing RSS for news or blogs any time soon.
I’ve added a JSON feed to this blog because Manton created the WordPress plugin already.
Side note: How did I not see this one coming?