None of which means that you actually should switch back: Chrome is a great web browser. But it isn't obvious that you shouldn't.
Even if you don't use any add-ons at all. I've always taken issue with Firefox, it has the broadest support and community centered around add-ons - but if you actually use any add-on the browser becomes completely useless. I've been bitten so many times in the past that I barely trust any add-ons on any browser, eventhough I've only had issues with Firefox.
Hopefully it will be better now.
That has been the opposite of my experiences, I am sitting on 100 tabs with 800MB of memory used in firefox. Sometimes I have 200+ with 1.5 GB of ram used.
Actually, just looking at chrome://memory-redirect/ in Chrome, it compares firefox's and chrome's memory usage. Chromium 1,394,260k 877,088k (about 40 tabs) Firefox 889,576k 62,692k (about 100 tabs).
Now this is on Linux, but I haven't used Firefox on windows recently to compare properly. One good explanation for all this is that the tab-per-process model means that you have a memory overhead for each process, so you naturally have more memory usage per tab.
But not in terms of ui, tabs shrink till they hold no text in chrome instead of scrolling like in firefox.
The firefox tab scroll feature is probably the feature I hate the most, in any browser (yes, you can disable it - but bad defaults stink and you can't just go around and change the settings in everyones browser).
First time I've come across someone that doesn't hate it :o
I remember Firefox used to have the bad behaviour like chrome(back in the 1.5 days) and I would occasionally use an IE shell called crazy browser to do my extremely many tab surfing(I also used 2 browsers partially so I could surf something else while 70+ political blogs or webcomics were loading since browsers tended to freeze for a long time on that back in those days).
I much prefer the Firefox tab scroll feature, compared to Chrome's way of handling tabs. The handy "show all tabs" dropdown is nice as well. Between the two, I find managing large numbers of tabs to be easier and less painful in FF than in Chrome.
YMMV.
Ultimately, Chrome exists for Google to increase it's advertising profits. It's a clear conflict of interests.
Plus, Firefox is a great browser and works really well on my reasonably high spec'd laptop, so it's not so difficult to be idealistic here.
> Gmail + Google Calendar + Chrome + Google Drive + Google Search + Google Docs + Android Phone + Google Maps + ...
What about: Gmail + Google Calendar + Firefox + Dropbox/Wuala + DuckDuckGo + Live Docs + Android Phone + Nokia Maps + ...
Of course, you could go Google free if you want, I just pointed the alternative that doesn't regress in usability and convenience from what you currently use.
I've been looking for a good, self-hosted version of Gmail that can replace my POP for a while, but the main reason why the lure of Google is so strong is convenience. And cost. And to some extent, reliability. Living a Google-free life is definitely doable but it can come at a cost (time, expense, convenience, functionality, reliability). That's the main tradeoff.
GMail supports IMAP, but then so do many other mail servers.
(You can also use a web front end like RoundCube, if you want to.)
Now I realize that any tiny reduction in perceived speed (not due to slower JS or loading, but probably some of chrome's UI speed tricks) is made up for by the lack of a context switch between terminal and browser.
It pains me because I have to restart Firefox every few days or else it turns into a slow, memory-eating blackhole. But, sigh, I cannot live without that extension.
I do believe in the mozilla mission for an open web, and it's got fairly comparable performance overall, so I use it for my main browsing / firebug. Chrome's for flash-heavy sites and playing with webrtc occasionally.
Inspector on chrome has certainly become quite good -- I've missed firebug less and less over time as I started using it. Though Firefox's new built-in developer tools are really sweet and might add enough functionality for me to miss in the near future. They're adding a command line thing that is super cool!!
I may be over-thinking this, but in case you didn't know, Flash Player in Chrome is still developed mostly by Adobe. Chrome has a different plugin API, I think, and some extra sandboxing, but the core parts of Flash Player in all browsers come from the same Adobe-owned codebase, including Chrome's bundled version.
But the bulk of my tabs are open in Firefox, and I prefer Firebug over the Chrome console for development
These days Firefox feels just as snappy as Chrome to me, though this has only recently been the case in my experience.
This is pushing me to use Chrome for those reasons - so I hope that FF fills whatever gap is causing sites to exclude FF (oh, and IE, Opera, etc.)
This seems unlikely as FireFox user share was bigger then Chrome until recently and is much bigger then Safari. Except for Mobile, where I think the dominance of Android/ios has led to a lot of use of webkit specific features.
http://superuser.com/questions/257102/why-doesnt-chromes-adb...
Since Chrome 14 (i'm not totally sure about this version) WebRequest api where implemented, but only as experimental api (you would have to enable them from chrome://flags), and Chrome >17 enable them by default.
So Adblock Plus >1.2 beta [2] and Chrome >17 should block ads just like Firefox. It's possible that there are some small difference, but that's likely a bug and should be reported.
[1] http://adblockplus.org/development-builds/experimental-adblo...
[2] http://adblockplus.org/releases/adblock-plus-12-beta-for-goo...
I'm not sure what's the situation with other adblocker for chrome.
Chrome is easily the worst browser on the market, short of IE <= 7. It is slow and grossly unstable. Across multiple computers and OSes, across the past few years, this has been my consistent experience with Chrome, so it's not just my current install.
I would rather use IE 8 than Chrome. As a web dev, I loathe my time testing in Chrome. When a bug report comes in, more times than not, the answer to "which browser?" is "Chrome" because V8 is buggy as hell. And the developer tools are simply worthless because they inject markup into the freaking DOM.