3 ms·
As someone who converted from Firefox to Chrome, I think this mostly sums it up pretty well. Especially the part about being community-driven and then not liste
by josteink 14y ago
As someone who converted from Firefox to Chrome, I think this mostly sums it up pretty well. Especially the part about being community-driven and then not listening to the community.
I see others have also mentioned memory-usage and that is also a fair point. At some point, Firefox would have memory leaks so huge that it spent most of its CPU time constantly trying to GC, slowing to a complete halt.
And then, just like with the updates, you had to restart. Restarting Firefox was a pain. But somehow restarting Chrome when updates come along is not. Why is that?
My desktop is a quad-core system with hyper-threading. That's 8 logical cores for the machine if utilized correctly. By Chrome having a process-per-tab model and Firefox not, everything else being the same Chrome can reduce its startup times to 12.5% of that of Firefox. It's an order of magnitude improvement.
You don't care about restarting Chrome because it just takes one second and you are back where you started. Firefox takes almost 10. That's way beyond annoying your users.
When you are the browser spending ages doing a restart, you're not in a position to force updates on your users.
Another thing which I haven't seen mentioned anywhere, which has been broken in Firefox since the very first releases is the add-on and add-on compatibility checking. It's retarded and I cannot believe it hasn't been fixed yet.
The typical Firefox update process goes like this: 1. Firefox informs you there is an update and you need to restart. 2. You accept a restart 3. Firefox shuts down, updates, and restarts. 4. upon restart after the update has been installed, it checks if your addons are compatible. WTF?!?
Usually that works out fine, but every now and then it doesn't. And then it's too late. That's retarded.
Why on earth would you check compatibility when it is already too late to do something about it? The process should be re-ordered. Compatibility checking should be done first. Then Firefox could say "There is an update and all your add-ons are compatible. Would you like to update now?".
A simple re-ordering of things it already does would have solved one of the two biggest issues people have with the update-mechanism. Why hasn't this been done already?
I'm a Chrome convert now, but I keep coming back to Firefox to see if things have improved, because I really believe in what Firefox stands for and what it represents. Unfortunately, I keep coming back to Chrome because for me, it just feels like a better browser.
- Jgrubb 14y agoI did the exact same thing last year. Tried switching back from Chrome to FF and using FireBug again. FF kept crashing on me. Gave it two days, switched back to Chrome.