03 Jun 08 Why did Google name their Browser "Chrome"?

Usage of word,

If you are wondering why Google named their browser, “Chrome”, here’s my opinion.

First Hint

At the first sight of Google “Chrome”, I thought it was basically a modified version of Firefox, based on the same open-source Gecko engine used by Firefox.

Another Hint

Another hint was that the default GUI theme is called, “Chrome” for Firefox. (As a Firefox extension developer who have developed the SiteHoppin Toolbar for Firefox, I can contest that Chrome has always been a widely used term for Firefox programmers.)

Proof

If you don’t believe me, take a look at this directory (H:\Documents and Settings\max\Application Data\Mozilla\Firefox\Profiles\xdorv70b.default) in your Windows system file where you should rename “max” to your Windows user name and xdorv70b.default would be something-similar.default.

If you open up extensions directory from there and open up any of the directories inside it, (each folder is a Firefox extension) you will probably notice that almost every Firefox extension uses a file called, chrome.manifest. (Yes, even file names with “Chrome” in Firefox)

To sum it up, I am not saying Google Chrome was taken from Firefox but only that “Chrome” has always been widely known among the Firefox Development crowd.

Coincidence or not, you be the judge. Tags:application data, coincidence, crowd, documents and settings, firefox extension, gecko, google, Google Chrome Hacks, modified version, open source, profiles, programmers, windows system, windows user

Filed in Google Chrome Hacks with 4 Comments

03 Jun 08 Google Chrome has its own "Task Manager"!

The biggest difference between Google Chrome and Firefox/IE is the fact that Chrome has its own Task Manager.

To access the Task Manager in Google Chrome, goto Developer->Task Manager menu as shown below:

As you will see, the Task Manager is very accurate with stats of memory, CPU, and network of each tab, plugin, and the Browser itself. (Now these are actually all different processes in the actual Windows system’s Task Manager too, you can look here for some more info on that.)

Of course, the point of having a Task Manager is that every Tab is managed more efficiently plus you have one window for ending any processes that are causing frozen-windows or simply taking too long to load.

If you click on “Stats for nerds” under the Task Manager, you will also get to see even more detailed stats on the processes running. This sorta reminds me of a Linux system where every detail is accessible by the user unlike Windows.

Our verdict is that the Task Manager on Google Chrome is even better than Windows operating system Task Manager as you get what you see.

This Task Manager might be a great way for developers to add more functions, especially since the Google Chrome is completely open-source. (Yes, you can build your own browser on top of it if you want) Tags:Chrome Features, developers, google, linux, linux system, manager menu, memory, nerds, open source, sorta, task manager, windows operating system, windows system

Filed in Chrome Features with 0 Comments

03 Jun 08 Google Chrome Launched with Multi-Threading Technology!

Google Chrome has just been launched (and of course our new Chrome Hacks blog along with it) with multi-threading technology that makes use of multiple processes (in Windows system) instead of traditional 1-process approach. (which is taken by IE and Firefox)

It’s still unclear how beneficial Google Chrome’s multi-threading technology is but in my experience, it does help.

You can read more about Google Chrome’s multi-threading technology over here.

Here’s an excerpt from Google Chrome Page:

Under the hood, we were able to build the foundation of a browser that runs today’s complex web applications much better . By keeping each tab in an isolated “sandbox”, we were able to prevent one tab from crashing another and provide improved protection from rogue sites. We improved speed and responsiveness across the board. We also built V8, a more powerful JavaScript engine, to power the next generation of web applications that aren’t even possible in today’s browsers.
This is just the beginning – Google Chrome is far from done. We’ve released this beta for Windows to start the broader discussion and hear from you as quickly as possible. We’re hard at work building versions for Mac and Linux too, and we’ll continue to make it even faster and more robust.