It has been 6 weeks since I decided to try Google Reader over NetNewsWire (NNW) and I wanted to share some results. For pure speed and layout I think NNW does a better job. For nearly everything else, I think Google Reader does a good enough job that I am sticking with it. NNW was removed from my Dock weeks ago.

The portability is just too attractive with Google Reader. I don’t have to have my PowerBook with me to keep up with feeds – I can just hop on any computer with Internet access and catch up.

If I have one big complaint with Google Reader it is with performance when there are a lot of feeds. I believe this is more to do with the Apple environment than with Reader, as I don’t see any real lag as I use Reader on a WindowsXP system. When I use it on my PowerBook I know that I can get the processor up and the fan blowing by moving through the Reader items too quickly. I like to use the J and K keys for forward and backward navigation and I keep my view set to All Items (G A keys) and show Only List Updated in the subscriptions areas and Show Only New in the items area. Get moving too fast through your feeds using the J and K keys on a PowerBook and you will probably see what I mean.

What is the technology behind Google Reader? Any java in it at all? I ask because it seems like java-based things tend to heat things up on my PowerBook by cranking the CPU. High CPU=high heat. High heat=crank up the fans.

But, I’ve learned how to work around this issue by going back to the home area (G H keys) and then coming back to the All view. From there I can move through the unread items pretty well until I start doing too much back and forth with J and K. You can tell it is coming because everything is moving item to item really fast and smooth when all of a sudden they just get slower and slower. If you use something like MenuMeters or Activity Monitor you can see that the CPU is at, or near, 100%.

It’s not enough to deter me from the portability of the web based reader though. I’m sticking with Google on this one.