Chrome is Google’s latest product and it’s in beta [hurhur] for now. The need for Google to write its own browser is explained here and they clearly state that they’re happy to let other developers take visual and idea cues from this project to work on their own browsers.
The installer is a measly 427kb and takes all of 2 seconds to install. It automatically copies over any relevant Firefox bookmarks, preferences etc so there is no loss of productivity fom the get go. I’ll come out and say it right here and now, Chrome is NOT a pretty thing [for now]. The lack of polish is frighteningly obvious, and the over-simplistic design is likely to put off a lot of people. Maybe it’s just me, what with being too attached to Opera.
- Written from the ground up for the new ways in which we use the Web.
- A fresh new way to think of tabs
- Among the innovations are new ways of memory handling, basically each tab and each type of request is handled as a separate process
- A task manager for web browsers – with info on memory-intensive tabs and plugins[!!]
- Asynchrous JS + auto-timeout killing = SWEET
- The new v8 JS VM
- An ingenious way to prevent memory bloat as a direct result of #2
- Advanced security and NO popups, thanks to #2
- Google Gears built in
- Debugged and code-tested with Google’s infrastructure on the top sites surfed by audiences worldwide
- Btw, where are the ads? [yeah I’m pleasantly surprised.]
The decision to reinvent the browser is commendable. Google is right to say the level of sophistication we see in web apps today weren’t even dreamt of when the Internet and the first browsers came out so what we need is new code that handles such tranmissions uniquely [and better].
I haven’t actually done speedtests [I don’t know how] but Chrome is zippy.
It’s almost as fast as WebKit it uses WebKit, the same engine that powers Safari and we know how fast WebKit really is.
Tabs have been completely reworked in that previously, they just served as a convenience of loading different pages within one window, reducing the need to switch around. In Chrome however, tabs are windows in their own right and can be dragged off to form a new window. What this means is conceptually powerful. [Isn’t this a WebKit feature?]
The address bar is within each tab, and it’s also the search bar. Whatever you do within the tab is independent of the rest of the browser.
Since each tab also means a new process, any one process or page hanging will not theoretically hang other tabs.
The fact that every tab and request is process driven helps in the the security aspect because these “processes” not unlike desktop apps can be artifically nerfed to become sandboxed with only limited/minimal/zero rights to the HDD etc. This inherently makes browsing more secure in that even if harmful code is accidentally run, it cannot touch your data in any way. That said, plugins work outside the sandbox in a sense, and they may be insecure. Google has tried to stop this by making sure plugin code also runs in a spearate process but I guess this must be a continual battle against good and evil, as hackers will definitely try to circumvent the protections, and developers will work hard to secure all bases.
When other search engines or services are used eg Amazon, Facebook, Piratebay etc, their search handler shortcuts are automatically added. In a tribute to Opera, these new search engines can be searched with a keyword [tab] search+query easily.
Opera got Speed Dial right, but Chrome takes it further. In Chrome the user’s favourite sites will be listed on the main page and the sidebar will list the most used search engines. There is no need for customisation and these lists are automatically populated. I guess it’d be nice if there were customisation options though.
And finally, in a bid to fulfil one of the mission statements, Chrome offers the ability to bookmark webapp pages like GMail etc as a “Chrome application” with its own icon on the desktop. When these are clicked, they load Chrome without the address bar and browser buttons etc, so it’s just like a desktop app, not unlike Prism and Adobe AIR, except it’s built into the browser. Pretty powerful stuff if you use it right.
The garbage collection gets a overhaul mainly because v8 keeps track of the “address” of all variables/classes/objects as well that values they contain as well independently. As such, there will be no confusion if the number 15 is staying at house 15 for example. The “memory” for addresses also means that when these variables are no longer needed, the entire address can be bulldozed, not just the occupants.
The most amazing part about all this is…v8 is independent and freee for use in EVERY browser. Google Chrome uses it in the same way as a plugin, by means of an API, and that means any browser can as well. Fingers crossed for Opera.
Having Google Gears built in makes Chrome preferable to Mozilla software with Gears plugin for accessing GMail and Google Docs for now. If you recall, the Google Gears API serves as a offline cache so that services that use it can be run even offline. The “files” that are created reside on the HDD until the next time you go online, at which time they auto-sync with the online storage and service. If you use Google Gears a lot, then you will know just how much this boosts productivity.
Again, Chrome is an ugly duckling for now, I really don’t like the pretty bland windows. Coming from the Mac camp, the lack of minimum amount of visual appeal is not a sight for sore eyes. However the code is powerful and it’s open source. Google is actively inviting developers to take their code and run with it; so if Google really means for Chrome to be a “framework” for browsers to come, then I can’t wait to see what the future holds.
, web technology