Multi-process Architecture in Google Chrome
The folks over at Chromium Blog have posted a lengthy write-up on multi-process architecture and how it applies to Google Chrome. It’s a must-read if you’re interested in this kind of thing.
The folks over at Chromium Blog have posted a lengthy write-up on multi-process architecture and how it applies to Google Chrome. It’s a must-read if you’re interested in this kind of thing.
Wired.com has an extensive write-up on the people and reasoning behind Google Chrome. It’s an interesting read, and helps put the whole venture in context.
Google’s answer to the question no-one asked landed today with the launch of their Chrome web-browser. And it’s actually quite good. It’s light, very fast, very easy to use, and does have some features to love.
Getting the most attention is V8, a new JavaScript interpreter Google engineered from the ground up for raw speed. It’s noticeable too, pages with a lot of client-side code are demonstrably faster than in Firefox and Internet Explorer.
Other distinctions include a very tidy interface that looks great on Windows Vista (Chrome is also available on XP; Mac and Linux users will have to wait a bit longer to get their hands on the beta) and a nice model wherein each tab operates within it’s own process; if the tab content is slow or crashes, the rest of the browser remains unaffected. It even includes a task manager to view the memory and cpu usage of all active tab and plugin processes (in fact, if you have other browsers open, it will include their resource information along side Chrome’s).
It’s not perfect, and is clearly still in beta. While stable, many killer features are still missing, like bookmark management, RSS feed integration and a proper plugin model. Also, the lack of a dedicated search box is really annoying for longtime Firefox users, although this concern may fade with extended exposure (Chrome’s navigation bar doubles as a search box, using keywords and shortcuts to choose a search provider). On the other hand, it does automatically add search engines to it’s collection when you use them (go to amazon.com, and moments later amazon search is listed in your search engine providers).
Overall, Chrome is a very promising entry into the competitive browser market, and while obviously an early product missing some important features, it is stable and usable for those who don’t require some of the complexities associated with Firefox.
IGN and Google have mapped Liberty City, featured in the just-released GTA4. Places of interested are already cropping up, thanks to the community. This is just another reason in the list of many testifying to the sheer brilliance of Google Maps.

I’ll say it again: Google needs to buy Remember the Milk.
Remember the Milk is a task-management web-application. This may not sound like much, and rightly so, task-management applications are beyond ubiquitous, but it really is an exciting product that blows away many of the conventions associated with your average productivity application.
In particular, the RTM folks have spend a lot of time integrating their product with others, including three from Google (Gmail, Google Calendar and iGoogle; it also uses Google Gears for offline access and Google Maps for geo-tagging tasks). So, is Remember the Milk an obvious target for a Google acquisition? Clearly not, or they surely would have indicated something by now.
Nevertheless, this is an application that they should firmly set their sights on, particularly as they take the company into more corporate territory with Google Apps, where Remember the Milk could be really useful. The Gmail integration (achieved with the use of a GreaseMonkey-style Firefox plugin) should be enough to convince anyone; if RTM was available to everyone in Gmail’s sidebar I have no doubt the vast majority of users would find it useful. It’s a uniquely suitable place to locate such functionality: everyone views their email every day, a lot (like me) keep Gmail open for hours on end.
Come on Google, this is an easy one.