Google Chrome on the Mac

For those of you that like being on the bleeding edge, developer builds of Google Chrome are now available for OS X.  In this article I'll summarize the functionality of the most recent build.

Google Chrome for the Mac is undergoing heavy development.  As of this writing, the most recent build is build #16355.  When I say heavy developent, I mean it.  On average, more than twenty builds are generated every day.  Having Chrome available on the Mac means that Chrome testing may be performed without having to launch an expensive virtual machine.

I've been using Chrome as my default browser on OS X for more than a week.  Here's my findings:

The Good

  • Builds have been stable with few crashes
  • Most websites render as expected
  • Chrome is fast.  Javascript execution flies.
  • All tabs run in their own thread and are accessible from the Activity Manager
  • Dragging of tabs outside of the browser is supported
  • History and bookmarking function as expected
  • Overall functionality is solid and usable, with a few caveats

The Bad

  • HTTPS is not supported
  • Downloads are functional, but no progress bar is provided to the user
  • Google docs is not fully supported.  I found that I was unable to rename tabs in a spreadsheet.
  • Flash is not supported
  • Java is not supported

Summary

Chrome for the Mac is functional and usable.  You will not be able to watch video or run any Flash, Flex, or Java within your browser.  Downloading files works, but lacks good user feedback leading to a frustrating experience.  For general web browsing, Chrome performs well.  I recommend you kick the tires on it a bit and monitor its progress, but don't rely on it yet as your primary web browser.

Comments:

Processes, not threads

by Harel on May 20, 2009 at 5:07 AM CDT
Each tab runs in a separate process, not a thread. A thread would not have shown in Activity Man.

Functional and stable?

by Bart on May 20, 2009 at 5:24 AM CDT
In what way can you call a browser that lacks HTTPS, Flash and Java functional? And why should you call a product with "few crashes" stable? I suggest you raise the bar a bit...

Why is it so hard to port it to Mac?

by oLdsk3wL on May 20, 2009 at 6:25 AM CDT
Maybe I am a little bit off here, but why is it so hard to port it? If they should have used QT then at least the UI part would have been taken care of.

It's useless

by jgarifuna on May 20, 2009 at 5:56 PM CDT
I tried chrome on my mac and it was literally useless. It kept crashing.
Subject*
Name*
Comment*