This past week I have gravitated to using Google-Chrome and Chromium more and more and I have to say I am loving it. Everything just works, and works rather snappy. The biggest contention I have with web browsing would be the results of Flash being a friggin hog and tending to crash the browser. I have not noticed as many problems with Flash under Chrom(e|ium). No slow downs, mouse interactions work, and multiple flash elements on a page do not destroy the performance.
I installed Chrome on my wife’s eeePC and she is just loving it. That is where she spends all her time now. “Amazing” she says! She confessed the other night to absolutely loving Google-Chrome.
What can I say? Google has done a bang up job with this browser. I am even using it more and more at work! My only gripe, originally, was with newly created tabs spawning next to the current tab I was in. I had been accustomed to the tabs spawning at the end of the tab row. There is a plugin to alter this behavior called tabby. What tabby does is move the newly created tab to the end of the tab row after it is created. The effect is noticeable as you see a bit of “jumpiness” in the tab bar. Not that distracting and you eventually begin to ignore. But, I must admit that I can see the benefit of tabs spawning next to the current one and I am tempted to go back to this behavior.
The latest builds of Firefox 3.6 seem to default to this behavior. To fix it you have to go into about:config and set browser.tabs.insertRelatedAfterCurrent to false. Chances are you will get warnings that this may violate your warranty. I never knew there was a warranty for Firefox. Anyway, be aware that this warning has a checkbox that says don’t show me this warning anymore. If you don’t click it you will get that message every time you start Firefox.