Google Chrome » Rocks

So my first impression about Google's new Chrome browser, is that it Rocks. It's quite apparent that the engineers at Google know exactly what the development community is looking for and they make no small feat in creating a web browser that is able to completely annihilate the competition. Moreover, I really like some of the features that are included by default like the Firebug style DOM inspector that you can invoke by a right click context menu (Nice).

In my first shot at testing out the new browser's speed, I attempted to pull up a Google Map that I have on my site which makes a remote call to Google's GeoCoder object to retrieve coordinates for a city to update the map locations based on those coordinates. Though I should actually have the coordinates in a Google GeoCoder Cache to speed up the process, I don't » yet.

The results were amazing. while it took Firefox 2 approximately 4 seconds to fully display the map image, it took all of 500 milliseconds for Chrome to display. My results are just from personal experience though. Google claims that Chrome's new JavaScript engine, V8, shows remarkable performance levels and they provide a collection of benchmark test results to boast. [Chrome Test Results.]

According to the developers over Mozilla, the new browser is not as impressive as Google may claim and they also ran some tests on Chrome with a JavaScript testing engine named SunSpider. Mozilla claims that the new TraceMonkey JavaScript engine slated to be included in a future edition of Firefox, will perform even faster than V8. Things really start to get interesting though when JQuery's inventor, John Resig, decided to run some of his own performance tests on Chrome. In short » John agrees that Chrome's JavaScript engine is really fast.