Feed Readin’

Sunday, October 15th, 2006

I’ve been using Bloglines for ages as my preferred method for reading RSS feeds, but I think I may be ready for a change. Google Reader has been revamped to be much more useful than its previous suckful incarnarnation, and it now does two things which I really need: 1) It loads progressively— ie the more entries you read the more it loads, and 2) It sorts by newest even where there are multiple entries from the same blog. Check it out, especially if you’re already a gmail user:

With Bloglines, once the massive "all items" page has loaded then all entries on it are considered read, which means that if you get halfway through it but then close your browser, when you come back to it later you won’t see those unread entries again. If you have limited bandwidth as I do this also means the page can take a long time to load. Google reader loads 20 entries at a time, and tracks read items as you scroll down the page (also because by default it uses a newest-first order you are free to continue reading into older entries).

So dear Bloglines, screw you and your lack of innovation, there really is no excuse for not improving a web based application— unlike us poor sods in the world of desktop applications you have the luxury of rolling out a new feature any time you want, so when you fail to do this you piss me off. Google’s initial offering was crap, so they just replaced it with a better version, and you should consider doing the same.

feed

5 Comments

  1. andrew says:

    I ditched Bloglines because it wasn’t working so well with Safari: huge memory use and locking up the browser every time it refreshed. That may have been Safari’s fault, I dunno. But now I just use Safari’s built-in RSS reader. It ain’t great, but it does.

    Google Reader apparently does not support http authentication. That means I can’t use it for my Daring Fireball members’ feeds.

    Oh BTW, the tab order on the comment form seems a bit awry.

  2. richardn says:

    ah, tab order - one of my personal beefs, so annoying yet so trivial yet so annoying yet…

  3. mark says:

    I think the reason Bloglines is such a strain on a browser is the whole page is filled using Javascript (try viewing source, it’s hideous), presumably to make it harder to create meta feeds which utilize bloglines’ bandwidth and aggregation.

  4. AndrewR says:

    Like you, I switched to Google Reader from Bloglines. After about a week I’m back.

    Google Reader is nice but it would freeze up too much and I hated how it scrolled the post you cliked on to the top of the window, even if it was already completely visible.

  5. mark says:

    I’ve noticed some flaky behaviour too (including the unwanted scroll on click, and some keyboard focus issues… do you use firefox?)… but still like the overall functionality better.

Leave a Comment