Subscribe

  • Subscribe  

One Week Later: Chrome is not ready

Posted by Charles | September 13, 2008 .

I’ve tried Google Chrome for a week. Everyday during the week I tried to exclusively use just Chrome for my browsing part of living but failed. Reaching the week end, I find less and leas reasons, beside curiosity and mental attachment to the name “Google”, to continue using Chrome.

Here are what I don’t like:

  • It was very problematic whenever started using plugin, PDF and Flash. Even it may has others but these are the only two plugins I’ve encountered.
  • Once opened more than 5 tabs it starts eating more memory (and CPU cycle) than Firefox. Then my laptop fan would start annoying me.
  • I had to go back to Firefox for taken-for-granted toolbars such as Stumble Bar.
  • I had to go back to Firefox for those addons I’ve been using everyday, such as Delicious.
  • I had to keep Firefox open because I kept going back.

Here are what I like:

  • I starts fast and with just about 27MB comparing to about 90M when Firefox starts with blank page.
  • Regular page loads faster.
  • It works just like a browser.

As I wrote earlier this week, I believe Google believes the huge potential with Chrome. But potential doesn’t make my life any better today. Therefor, I quit Chrome for now.

Leave a Comment

If you would like to make a comment, please fill out the form below.


Name

Email

Website

*
To prove you're a person (not a spam script), type the security word shown in the picture. Click on the picture to hear an audio file of the word.
Click to hear an audio file of the anti-spam word

Comments

*
To prove you're a person (not a spam script), type the security word shown in the picture. Click on the picture to hear an audio file of the word.
Click to hear an audio file of the anti-spam word


Related Posts

6 Comments so far
  1. akae  September 13, 2008 9:56 am

    I agree. It doesn’t fit my navigation habits, but it is fine that some cool ideas it proposes will soonly be adapted by firefox.

  2. Jim  September 13, 2008 11:28 am

    Of course it’s not ready. That’s what “beta” means. If you want to use software that is ready for end users, then I suggest you stay away from anything that is beta.

  3. TJ Downes  September 13, 2008 11:46 am

    There’s also considerable issues with fairly standard javascript as well as varying behavior for Flash applications. Overall the concept is great, the app needs a ton of fine tuning before I’ll use it everyday.

    Also, horrible as a Flash debug platform. Chrome crashes whenever you terminate the debug session

  4. JTtheGeek  September 16, 2008 1:00 pm

    I agree with you on most points. Having the tool bars is a must, and there are quite a few things that need improving, however, as a first release beta of the browser it’s simply astounding. I really hope Google puts a lot of effort into the finishing touches and releases a final version in a short time period. I am a little worried though, after all, GMail is still in beta. It feels like Google keeps things in beta as their excuse of having unresolved bugs.

  5. Sravan  September 17, 2008 4:17 am

    The beta version was more to generate buzz and so Google’s concentration was on making Chrome unique. Its timing was also such that it stole a lot of attention that IE8 was supposed to have got.

    Adding toolbars (the absence of which annoys me too) and allowing users to set more preferences must be something they would take care of for the final release.

  6. DeadCell  June 15, 2009 6:02 pm

    Of course it’s not ready. That’s what “beta” means. If you want to use software that is ready for end users, then I suggest you stay away from anything that is beta.

    Umm… Not really. Google just uses that as a way of explaining bugs. How many years has Gmail been in beta?!?!?

    In 5 years, Chrome will either be gone, or still in beta.

<

Direct TV Offers - usdirect has the best directtv deals