| Sorry to see you downvoted. Seems like a reasonable question. For me, Chrome starts and renders my default page faster than Firefox. Noticeably faster. I'm not sure if, when following a link that one is faster than the other, since server response time is a factor. However, I've had far fewer cases of of frozen pages with Chrome, and have never had all my tabs and browser instances of Chrome get locked up because of one page page. Firefox, on the other hand, is monolithic in that way. There is one feature of Firefox that is essential for me: invoking firefox from the command line (or a shortcut) starts a new instance. Chrome seems to (usually) want to find an existing instance and open a new tab. I seriously do not want to have a single browser instance with all my tabs; I prefer to have multiple instances with related tabs. It's especially annoying when kicking off a link in chrome opens a tab in an instance in some other virtual desktop. :( OK, Chrome rant over. Chrome has gotten better about supporting bookmarklets and greasemonkey, key aspects of my Firefox use, and overall memory use is much better for me with Chrome. |