Browser Wars - enter Google Chrome

Browser Wars - enter Google Chrome

Google launched just launched Chrome (, an open-source browser, built with today's internet in mind. The biggest features seem to be a new memory architecture, where each tab has its own process, lightning-fast javascript execution and, as expected, its own look&feel.

Google Chrome is based on WebKit, like Apple Safari browser, so your applications will most-probably look the same in both browsers (some CSS3 properties seem to be unsupported, though). Since it has its own Javascript engine implementation - V8 ( - we can't count on Javascript running just the same way.
By using Javascript frameworks, like Prototype or JQuery, we're normally safe from most browser javascript differences. Some errors in Chrome have already been reported in both frameworks, so beware. The frameworks seem to have some catch-up work to do.

Chrome also has built-in support for a Google technology which might still come to re-define applications, as we know them - Google Gears, or just Gears ( Gears enables web applications to run off-line, meaning without an internet connection!

So, what does this mean for us, working with OutSystems?

It means, unless we defined as project start our target browsers, we have 1 additional browser to worry about. If the application being built is for Internet users (Extranets included), then this additional concern should be included.

For reference this is the browser share distribution of access to, just 3 months ago:
IE7: 39% IE6:30%
Firefox: 25%
Safari: 2,5%
Opera: 1,5%
This meant, in order to support 99% of the browsers, one had to worry about 5 browsers.

Enter Google Chrome...

According to different web sources, Google Chrome ate something between 1 and 2% of market share in the first 24h.