Wow, the Safari thing was short lived, huh? OK, here’s the deal with that. Remember how I said I was going to try the Google Reader for a week to see if it could replace NetNewsWire? Well Google Reader is pretty good once you learn all the hotkeys that matter to you.
For me I need the view all look, only updated subscriptions, sometimes full screen, and learn to use j and k to cycle forward and back. It works really well until Safari starts consuming 100% CPU for 5-10 seconds every 10 time you hit the j key. I’ve been searching everywhere for the solution to Safari getting slower like that, but I haven’t found the solution yet. Cleared the cache, no favicons, etc. I have my suspicions that it has something to do with Java or javascript, but I can’t prove it. While this may not be a big deal to some, I am doing everything on a PowerBook so when the CPU hits 100% for extended periods of time the fan kicks in and the thing gets hot.
So I downloaded the latest nightly build of Camino and it is way faster than I remembered. I guess I’ll stick with it for a while and see how it does. One thing I noticed this week since I now use Google Reader for my feeds I can keep up at lunch from work. At work I run Windows (Windows2003 via Citrix actually) and Google Reader via Firefox on Windows is way smoother than my Safari or Firefox on OS X experience. No lag, very smooth, no runaway processor, etc.
Anyone else ever see anything like this? Should I wait and see if Safari gets any better with Leopard? Should I just stick with Camino? Will there ever be 1 browser for OS X that meets all of my needs?