Developer perspective: Google Chrome

Today, Google officially launched the Chrome browser. The installation is still a Google-style overhead. After clicking I agree, the installation process is started directly until I prompt whether to import iesettings. The natural path is in drive C, and there is no choice. There are a lot of chrome websites on the Internet now. I 'd like to open a new page at the startup, which looks strange.

 

The address bar introduces the same mechanism as the Firefox plug-in to mark the current domain with a dark color. Although I personally think it is meaningless, It is the WebKit kernel, but I still tested acid3 with a score of 78.

 

Although sunspider is a WebKit test, it is considered a more useful test. Chrome spent 2835.4 MS +/-3.4% on sunsipder. To make a comparison, it lists the time consumed by Firefox 3.0.1 build 2008070208 on my PC as 4565.6 MS +/-3.9%, the time consumed on safari 3.1 525.13.1 (this version is not new) is 6111.2 MS +/-4.9%, and the test result on opera 9.52 is 6694.0 MS +/-1.8%. It seems that Google's V8 engine is better.

 

We can see that Google gears has been built into chrome, which is undoubtedly a good news for many developers. Using Google gears, we can develop more powerful offline web page applications. In addition, chrome also has built-in support for flash. I don't know if it is good for some people who love simplicity.

Let's take a look at Google's awesome bar.

 

Google's amazing Address Bar provides options for search results in Google, and even guesses about the word items the user wants to search for, which is indeed awesome more than Firefox. But this address bar seems to be helping us change some bad habits. For example, the pull-down next to a vertex does not show the most recent access record, but directly reload the current webpage.

Now there are a lot of heavy web application effects. For example, a small website of the author uses a lot of JavaScript skills. How does Google support these skills.

 

I tried it quite smoothly, which shows that Dom update rendering is fast. The animation of the homemade scroll bar is also smooth. In terms of applications, the response speed is faster than that of Firefox.

In fact, what's even more amazing is that Google came with a developer debugging tool when it released the first version. The debugging tool interface is similar to firebug. Of course, there is no firebug details.

 

In short, Google does produce a wonderful browser, but it is clearly not his goal to replace Firefox with a complex function plug-in on my computer. Such a high-performance and concise browser should obviously appear on your mobile phone and your PC.