Google Chrome is a remarkably powerful web browser. When running on Mac OS it’s also an incredible power and memory hog. At least once a week it bloats so badly that it makes my desktop unusable. Starting today I’m going to take a trial run of living life without Chrome.
Since it’s Mac native, I’ve given Safari the honor of being the first test platform. Although today’s tests have been limited, it’s held up admirably – and more importantly hasn’t slowed the machine down to an infuriating place. As it turns out the threshold for victory in these real life tests isn’t going to be all that high. Anything that lets me get through a week without crashing the computer will likely get a pass as a better option than continuing on with Chrome.
There was a time I’d want to go out and try all the obscure browsers hoping to turn up something with wow factor to spare. These days, I’m mostly about simplicity in use rather than wow. I don’t care so much how the machine runs just so long as it does. I’m not going to spend a lot of time wanting to tinker around under the hood until it behaves “just so.”
I’d love to place all the blame squarely on Google here, but if I’m fair, I’m currently running a slightly more than 4 year old machine that was a touch under powered when it came out of the box. The ever increasing demand for raw processing power in a computer hasn’t been kind to my Mini. Truth is, switching browsers is probably the last ditch effort to coax a bit more life out of the machine before bringing a replacement online. If I were smart, I’d go ahead and make that purchase now instead of when something finally fails on me… but then needing to buy a computer right-the-hell-now after the old one has crapped out is pretty much one of my oldest continuously observed traditions.
Ditching Chrome won’t solve all that ails computing here, but it could well alleviate the most obnoxious symptom of aging equipment. For today, that would be more than good enough.