The rendering engine makes no difference at all to me. Whether Gecko or WebKit, both follow the standards closely enough that I know how something will render i

The rendering engine makes no difference at all to me. Whether Gecko or WebKit, both follow the standards closely enough that I know how something will render in one or the other without testing. Combined with reset stylesheets, which iron out little differences in default stylesheets, they're essentially the same. One thing that's great about Chrome is their rapid development pace. I think Mozilla has realised this is something that they need to change, and they're changing their release cycle to be much quicker (though, IIRC, not Chrome-scale). Firefox's extensions are what seals the deal for me though. Chrome's extensions are nowhere near powerful enough to do some of the things that Firefox extensions do with ease.