Hi, I was able to setup google chrome 64bit (the early dev access version) on my machine so just want to share my experience & build script for those who are interested.

http://sites.google.com/site/nguyen/...kware/packages

Feedbacks welcome. Thanks

You might as well warn potential customers that Chrome needs around 10gb in /tmp to build.

If you build from src then it might take that much - the method I use is installing the binary provided by Google

So how's it run, compared to firefox?

Much faster than firefox from what I heard.

Any chance this would officially get shipped with slackware?

it's insanely fast - comparing to Firefox. Still in very early development stage though and is quite immature, lacks of extension supports and configurations.

Maybe in some years when it actually has a release, is stable enough, has proven to be better than the alternatives & many people use it.

How is the speed compared to the Windows version of Chrome?
I would be interested in seeing someone run javascript benchmarks on both.

It is said that chrome run faster under linux than windows. Because chrome consume much RAM, and windows is poor in memory management. It will swap the application into virtual memories on disk if you minimize the window. If you want to bring it up, it takes long to wait swapping from disk to RAM.

I've never used Google Chrome, but have been running the daily Chromium builds for a few weeks now.

It's down right shameful how fast Chromium is compared to Firefox, Seamonkey, and even Konq. Flash takes less CPU in Chromium than Firefox. On one of our modestly powered machines (PDC 2140 1.6ghz x2), full screen high quality Hulu stutters quite often, in Chromium it is fluid.

On my E8400, watching Hulu in Chromium takes 19% CPU with 84M ram. Same clip in Firefox 3.5.5 take 27% CPU with 192M ram. Add to that the startup and shutdown time of Firefox that grows after usage, and the disk thrashing that happens because they want to put everything in an SQLite database, unless Firefox does something to compete with Chromium, I see it's user base going down.

Chromium is nice, I like it immensely, but it can't replace Seamonkey for me yet. My girlfriend used to run Windows in a VM just to play her flash based games, she hasn't had to since I put Chromium on her PC.

So flash on Linux isn't that good, and Chromium makes it usable. It is faster than Seamonkey, but not fast enough - or Seamonkey is not slow enough - to make me want to switch browsers. If I found myself needing to close and launch the browser often, maybe. I usually launch Seamonkey once, and it stays running for a week or so.

If you visit javascript heavy sites, Chromium is quite a bit faster. I personally don't visit these sites that much.
SunSpider JS benchmarks
Chromium 395.8ms
Seamonkey 2253.0ms
Konq 2635.2ms
Firefox 2071.6ms

And that tells me how important benchmarking Javascript is On this PC which ran that benchmark, in day to day usage, Konq is the fastest, then Seamonkey, in dead last is Firefox.

i used chrome in slack before, did not keep it for more than a few clicks. am too used to Firefox n' am too lazy to change.

however, it was really fast, stable and rendering performance was awesome.

although i don't see it being integrated into Slackware tree anytime soon.

In case anyone missed it, there is now a slackbuild for google chrome on slackbuilds.org:
http://slackbuilds.org/repository/13...google-chrome/
The google chrome slackbuild can be installed on both 32 bit and 64 bit Slackware. I am running it on Slackware 13 64 bit. It is indeed very fast and light.
Thanks to Erik Hanson for providing the slackbuild script!

Tried the slackbuild. After installing Gconf and ORBit2, it installed.

Now mit won't run, complains about nss libs.

So google has gone bye-bye. Wasted 45 minutes on this pos, not going to devote anymore time until/if it becomes stable, and actually WORKS on a default install of SW13/64 multilib.

Do you have seamonkey installed?
Also you might wanna try http://slackbuilds.org/repository/13...m/mozilla-nss/