Skip to main content

Google Reader Upgrade Dissappoints


Yet again, I find myself wishing I could say I like what Google has done with something, only to be forced into admitting: they disappoint me. Well, add one more to the list of things Google can't get right, even with an army of PhD holders and more money than you can shake a redwood forest at: Google Reader has gone from simple gold to contorted crap. The original version was a great excersize in simplicity in design that let me jump in, read, and get on with my life. The "upgrade" is a mess of a noisy interface for me to get lost in as my browser slows to a crawl with far more JavaScript than a simple reader needs, and even the occassional forgetting of everything I haven't read yet.

I was a little late in the Blogscene, which is a relative statement given that most of the world doesn't know what a blog is, despite the fact that most bloggers think otherwise. I started with my trusty KDE's Akregator, which is admirably usable, and then looked for a web-solution to use better from multiple boxes and a laptop, right around the time the first Google Reader was released. I jumped on board, and I loved it. Right off the bat you have your entire reading queue, waiting for you to read through one post at a time. Read, hit the j button, read, j, read, j, j (I skip things, a lot), j, j, j, read, j, read. If I had a backlog, I could just pick labels or subscriptions to read first and be on my way until I had time to read less important things. The key is it was simple. Most of the time, I only ever used a single button: the j. It was fast, showing just what I was reading and a few things coming up on the list. Thanks to (possibly accidental) details of the implementation, I could scrollwheel over the reading list and pre-load hundreds of articles, so that I could read them offline in my web-based reader! Again, best of all, it was simple. It did all this and it was clean, and simple. God, it was simple.

The new Reader is a beast. There is a busy tree of labels and subscriptions listed on the left, repeating my feeds for every label they are in. The unread counts are always inaccurate. It tries to show me everything I've read so far on the page, which adds up quickly. I can't mark anything as read without everything before it getting marked too, which means no holding things to read later. The javascript slows the page down and even locks up FireFox for a few moments when loading the next posts. it is not simple.

Google, use your many brains. I don't know how you could have messed this up so badly. It brings up an interesting question: is it OK to compete with yourself? They say that the new Reader meets the middle-ground between what everyone wants, but does that mean it doesnt actually fit what any one person wants? Re-release the original as Google Quick Reader or something.

I'm sorry. This post was badly written. Call it a rant. I just miss my reader.

Comments

k4ml said…
Interesting. I never use the old reader after a few try. I just don't like it so I stay with something simple such as feeds.reddit.com but right now, Google Reader has become my default.
Bob said…
Absolutely spot on!

I hate the way the new reader UI displays many stories on the same page and 'j' brings the next one to the top.

I reverted to the old UI immediately. I'll
be very annoyed if they remove it completely.

Popular posts from this blog

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…