Trying New Feed Readers

204 words.

Lately I haven’t been too thrilled with Feedly, so I was quite excited to find not one but three new web-based RSS readers: InoReader, Feedspot, and G2Reader. I’m assuming these popped up from startups trying to cash in on Google Reader’s demise.

But…

My excitment soon faded when it became clear that none of these are any faster than Feedly, which was my main complaint with it. What is wrong with all these web-based feed readers? They are sooooooo slow it’s painful. It’s like they’re all forked from the exact same codebase. Click the “update” button, then wait 10 seconds for the screen to do its AJAX-y update. I mean, is it just me? Is it my connection (my connection at work is actually pretty bad)? Are they transferring 20 gb of data back and forth with every mouse click? Is everyone’s server overloaded from new GReader-convert traffic? Was Google’s Reader that much more advanced than anything else?

Anyway, of the three, InoReader seems to be marginally faster than the rest so I’ll be trying it out for a while. I like the looks of FeedSpot best, though. (Although really, they are all three basically clones of Google Reader, almost down to the pixel.)

This page is a static archival copy of what was originally a WordPress post. It was converted from HTML to Markdown format before being built by Hugo. There may be formatting problems that I haven't addressed yet. There may be problems with missing or mangled images that I haven't fixed yet. There may have been comments on the original post, which I have archived, but I haven't quite worked out how to show them on the new site.

Sorry, new comments are disabled on older posts. This helps reduce spam. Active commenting almost always occurs within a day or two of new posts.