So I tried Google Chrome yet again on my Mac. For those of you not in the loop Chrome is still in development on Steve Job’s platform. Either way it was pretty nice, certainly faster than Safari and didn’t beach ball of death me for minutes at a time. The problem though? Well it has two helper processes that soak up 100% of this MacBook Pro’s processor. Honestly it was completely unnoticeable so the processes must be at a pretty low priority but once I was running on the battery and my little power indicator went from it’s usual 5.5 hours to 2.5 I figured something was up.
Yup it certainly isn’t ready for average users quite yet but is getting closer. Most of the features are there minus a few things like certificate management and plug-in support.