Why I Decided To Dump Google Chrome This Week

If you pick up tech journal, or read one online, chances are you are going to come across an article about Google Chrome, Google’s much-hyped Internet browser.  Actually, most of these articles would be more accurately described as love letters.  In them, you will read how fast Chrome uploads, how customizable it is, how it’s built upon a “multi-processing platform,” and how great Chrome is if you are a web designer or search engine optimization (SEO) guru.  With increasing frequency, you may even come across articles from respected trade journals criticizing other, competing web browsers, such as the popular Firefox browser.  An example of such a critique can be seen in a video from TR Dojo at Tech Republic here.

In fact, if you take a moment to research what is being written in the tech world about Internet browsers, you will find almost nothing negative about Google Chrome unless you take the time to read the comments at the end of some of these articles.  Read them, and you will discover a great many consumers complaining about Chrome’s recent tendency to crash – often – and the fact that, well, it just isn’t as fast at is once was.

Unfortunately, most of these voices are drowned out by the cacophony of Google Chrome lovers.  So, for this article, I thought I would tell you about my own personal experience with Google Chrome over the past several months and why I decided to dump Google Chrome this week.

When I first started using Google Chrome in its 2008 beta version, I must admit that I was not all that impressed.  Sure, it was fast in comparison to both Firefox and Internet Explorer, but it had virtually no customization.  Eventually, however, Google introduced its own “extensions”  for Chrome.  Most of these are, in effect, the same as Firefox’s “extensions.”  For those of you who are unfamiliar with Firefox, Firefox allows for extensive, feature-rich customization by downloading additional features and capabilities that the browser refers to as “add ons” or “extensions.”  Firefox also allows for the addition of “plug-ins,” such as flash or java, as well as the addition of “themes” which alter the appearance of the browser according to the user’s choice.

“Extensions” have been Firefox’s double-edged sword.  On the one hand, a persistent criticism of Firefox is that these “extensions” – when downloaded in quantity – tended to slow the browser down — often quite considerably.  On the other hand, Firefox’s “extensions” allow you to create your own, individualized Internet browsing experience.

Not surprisingly, once Google Chrome introduced Firefox-like extensions, the browser, in my opinion, began to lose its speedy edge.  Moreover, it now suffers from some of the same problems these extensions created for Firefox.  For me, the troubles seemed to begin with Chrome’s “Cool Iris” extension.  Again, for those of you unfamiliar with the application, Cool Iris is an image viewing platform that allows you to view your photographs, Flickr photographs, videos, TV shows, movie clips, and the like in a beautiful, gallery-like setting as shown here.

This extension has always performed perfectly in Firefox.  Unfortunately, whenever I used the extension in Google Chrome, it crashed.  More importantly, however, when Cool Iris crashed, the entire Chrome browser crashed.  Because of Chrome’s “multi-processing” platform, such wholesale crashing was not supposed to happen.  As a matter of fact, (and without getting into too much technical jargon) one feature that Google touted about Chrome was that it was built on a platform where what happens in one tab doesn’t affect what happens in another.

In other words, say you have one application running in one tab of Google Chrome and another application running in a second tab.  If the first application crashed on you, then only that application would close.  You would still be able to continue working with the second application, and the Chrome browser would remain open.  Admittedly, this feature was a significant improvement over Firefox.  Unlike Chrome, if the first application crashed in Firefox, the entire browser had a tendency to crash.

There is only one problem, from my experience — Google Chrome’s feature does not work, at least not all the time.  I consider myself a power user of any browser that I am using, and up until this week, I can honestly say that Google Chrome crashed on me at least 3 times each week.  It crashed on different machines and different operating systems (e.g., Windows XP v. Windows Vista).  And, what seemed to trip this crashing tendency was no longer limited to Cool Iris, which, incidentally, I continued to run without any problems on Firefox.

As I said at the outset of this article, I finally got to the point this week where enough was enough, and I dumped Google Chrome.  For me, an average of 3 crashes per week, coupled with slower operating speeds, is unacceptably high from a browser that touts its stability and speed.

Perhaps, my experience is an anomaly.  Nevertheless, I thought I would share it with you because the information on the Internet about Google Chrome is, in my opinion, erroneously one-sided.  I am not suggesting that you dump it as I did.  However, in an upcoming article, I will feature a list of other Internet browsers that you may want to consider if you are not happy with Google Chrome or, for that matter, Firefox.  In the meantime, I welcome your comments, thoughts, or suggestions about Google Chrome.  In particular, if you had the same experience with Google Chrome as I did but then learned that something else caused the problem, please let me know and I will re-examine the situation for a future writing.

Reblog this post [with Zemanta]

11 comments on “Why I Decided To Dump Google Chrome This Week

  1. Firefox is excellent. And after Google cut me off of youtube for not joining the g+ I use as little Google as I can. Not sure anything I do to my phone can seriously de-google it though. Other than that, done with those a–holes.


  2. I do not know whether it’s just me or if everybody else encountering problems with your website. It appears as if some of the text in your content are running off the screen. Can someone else please comment and let me know if this is happening to them as well? This might be a problem with my web browser because I’ve
    had this happen previously. Thanks


  3. I would like to show thanks to you just for bailing me out of this type of scenario.
    After surfing around through the world wide web and getting strategies that were
    not productive, I believed my entire life
    was done. Being alive devoid of the answers to the difficulties
    you’ve fixed by means of the post is a serious case, as well as the kind which might have badly damaged my career if I hadn’t noticed your web site.
    That natural talent and kindness in touching all the pieces was helpful.

    I am not sure what I would’ve done if I hadn’t come upon such a solution like this.

    It’s possible to at this point look forward to my future. Thanks so much for this reliable and results-oriented help. I won’t be reluctant to endorse
    the website to anyone who requires guidance on this situation.


  4. I have lived with Chrome too long, it gets slower and slower and more dictatorial each week. I need to escape but to where. Any way they don’t pay UK taxes. F/O


  5. Please remove Google Chrome from thi computer


  6. You can choose not to install any extensions. 🙂 The browser is far best from others.


    • Are you kidding me? So, what, you would tell someone to just drive with the windows down if their A/C doesn’t work in their?


      • …in their what? I assume you mean “in their car.” This is a fascinating, yet inept, choice of analogies. If someone had a non-working air conditioner in their car, and assuming it was as non-functional for said person as Chrome was for me when I wrote this blog post, then I might suggest to them that they get a new air conditioner installed in their car; i.e., try a new browser instead of Chrome, which is what I did. Chrome isn’t for everyone, surprise, surprise. It may interest you to know, however, that I have come to use Chrome again for somepurposes, and have written about it here and elsewhere.


  7. […] This post was mentioned on Twitter by Eric G. Young, Eric G. Young. Eric G. Young said: Why I Decided To Dump Google Chrome This Week: http://wp.me/pALwc-al […]


  8. That’s exactly what has happened to me in this past few days, since I installed the CoolIris extension! Way more crashes than before, sometimes just on some tabs and sometimes on the whole browser. And what’s worse, when the browser restarted it didn’t remember the tabs that were open, so I had to reopen them manually one by one.
    I thought it was the latest beta release that I installed on Monday, but it may be also some issue with CoolIrirs. I hope either way this will be solved!


    • while reviewing a browser
      should a beta or developer version need to be considered?
      Also Cooliris extension itself is buggy , Why blaming Google chrome For this.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: