[AJerman]

Originally Posted by iatacs19

I don't like Chrome for now, I need a damn home button to go to google so I can search stuff. Also, accessing the bookmarks is cumbersome, unless they are on the toolbar.

From Anandtech's tests Chrome is the slowest and IE7 is the fastest of all.

You don't need a home button. Just type your search into the "omni" bar. Learn a few of these key sequences:

CTRL+L: Brings you straight to the location bar, now you could just type what you want and press enter

If you actually want to go to Google, press CTRL+L, type "google" then press CTRL+Enter (automatically adds "www." and ".com").

And what's so cumbersome about the bookmarks? I put all mine on the bookmark bar, but if I had any extras, they are right there in the "Other Bookmarks" folder, or you can add more folders under that. Seems to work pretty much like any other browser to me.

Oh, and I read Anand's test and it sounds ridiculous to me. First off, he tested sites on the website which really doesn't test rendering speed at all. That just tests how fast your connection to the given site is at the moment. Just checking on some of the same pages myself, I can tell my times are vastly different than his, proving that it has nothing to do with actual rendering speed. Chrome is based off an updated version of Safari's internal rendering engine. It's not new news that new builds of Webkit are, by far, faster than any other rendering engine available at the moment.

Also, yes, plugins are on the way. If you read the documentation (comic book) before the release, they mentioned plugins serveral times. I don't see anywhere for them yet though, so perhaps that's a different beta further down the road.

Overall I'm very impressed. It has the best of every different world. The webkit rendering engine with added google engineering on top. I think this browser shows incredible potential considering it's only the first beta.

[iatacs19]

Originally Posted by MadDog

In the options, there's a checkbox to add the home button.

thanks!

[lauer87]

Firefox all the way

[ages944]

Originally Posted by BK

How do you benchmark the performance? I'd like to try that, too. I can't notice any speed difference as compared to FF -- not that I'm complaining, because both are fast, it's just that Chrome doesn't seem any faster. What am I missing?

Sun Spider Javascript benchmark:
http://www2.webkit.org/perf/sunspide...sunspider.html

- Tests the capabilities of a browser's Javascript engine.

[GAM3OVR85]

i would get it if it was blacked-out not chrome

[BK]

Originally Posted by ages944

Sun Spider Javascript benchmark:
http://www2.webkit.org/perf/sunspide...sunspider.html

- Tests the capabilities of a browser's Javascript engine.

Chrome definitely tests faster overall and faster individually on most of those tests, though oddly a lot slower for some of the tests (the "date" ones in particular). Once it gets plug-ins, maybe I'll start using it. FF is just so good I can't give it up yet, though. Maybe not ever. I've noticed Chrome has an annoying delay when you click on a link before the page opens. At least the first time you click on the link. I don't notice the same delay on FF.

Another thing I just noticed as I was trying Chrome, when I'm typing into a text box on e90post, I've gotten used to being able to select a word and, for example, hit CTRL-B to make it bold or CTRL-I to make it italic or CTRL-U for underline, and so on (this puts the UBB tags around the word). This doesn't work on Chrome.

[ages944]

Originally Posted by BK

Chrome definitely tests faster overall and faster individually on most of those tests, though oddly a lot slower for some of the tests (the "date" ones in particular). Once it gets plug-ins, maybe I'll start using it. FF is just so good I can't give it up yet, though. Maybe not ever. I've noticed Chrome has an annoying delay when you click on a link before the page opens. At least the first time you click on the link. I don't notice the same delay on FF.

Another thing I just noticed as I was trying Chrome, when I'm typing into a text box on e90post, I've gotten used to being able to select a word and, for example, hit CTRL-B to make it bold or CTRL-I to make it italic or CTRL-U for underline, and so on (this puts the UBB tags around the word). This doesn't work on Chrome.

I hear ya - Pandora is really slow for me. Remember that it's a beta though.

To me, the coolest thing about Chrome is not what it is now, but what it has the potential to become. There are some really good ideas behind the decisions made with this browser, and I am very excited to see where it all ends up.

[BK]

Originally Posted by ages944

To me, the coolest thing about Chrome is not what it is now, but what it has the potential to become. There are some really good ideas behind the decisions made with this browser, and I am very excited to see where it all ends up.

Yes, I agree. If it garners the same developer community support as is now going to FF, I'm all for it.