Keso’s Understanding of Google Chrome
4 Sep 2008 (Thu)GOOGLE’s NEW CHROME BROWSER, launched yesterday, promised to be faster, safer and smarter than other browsers. Key features include an Omnibox (where one can type in a website’s address or any search term), a Privacy mode (which ensures that traces of an Internet session are erased the moment one exits the browser) and Smart tabs (where tabs run on separate “processes, so if one website takes up too much resources or causes a software app to crash, that tab can be shut down individually).
For some reason though, I didn’t manage to install or run Chrome on my desktop PC yesterday. Still wondering whether that has anything to do a coincidental Windows update on the PC just before that. Anyway, I’m intrigued by what Keso has written about Chrome, in particular:
I think the real reason for Google to join the browsers bandwagon two years ago are this: Google needs control of a browser that has sufficient influence. It also needs to set up de facto standards through something that can be controlled and demonstrated.
Therefore, what’s important about Chrome are these two things: A new JavaScript engine V8 and a “Webified” version of the desktop app Gears. Both are part of Google’s key strategy to expand browser functions to better support future Web apps.
We often naively assume that Desktop battles are waged for the purpose of establishing Trojan horse pipelines. Actually, the smarter purpose of such battles is not for thievery or user base, but for the establishment of de facto standards that are advantageous to one’s future plans. For Google, this standard will enable its apps to run perfectly regardless of the platform or terminal that anyone may use. In order to better release its “cloud of accumulated energy”, Google needs a well-supported standard and a popular browser.
Therefore, Google has chosen not to integrate many of its own products and services into Chrome. Some people complain that one can easily install Google Toolbar on IE, but not on Chrome. Actually, there’re many more things that one cannot do on Chrome: visit Gmail with one click, publish easily from Blogger, upload video to YouTube, and even customize the default search engine…
Like Chrome, V8 and Gears are released as open-source projects. This will undoubtedly enhance their neutrality and therefore appeal to developers. It doesn’t matter how much market share Chrome will claim eventually. The key is whether it can provide the best demonstration of Gears and V8, thereby enabling them to become de facto standards.
Some people say that the target of Chrome is neither IE nor Firefox but Windows. Considering the line of “cloud”, apps and browser, I basically agree with this judgement.
- Roundup#3: 2007 Web Predictions
- 6 Essential Things to Know About Google’s OpenSocial
- The Ultimate Mobile PC?
- Insight#4: Of Alexa, Dmoz & Technorati
- If I were Google…
- Time’s “25 Sites We Can’t Live Without” in 2007
- Insight#2: Antidote for Babel Babble?
Posted by J.K. in *Insights, Business, Possibilities, Strategy | blog reactions | 14 Comments |

As of today, the 

