5 ms·

My neutral (?) view on firefox/chrome: - Firefox uses way less RAM - Chrome is usually faster/smoother, even if not by much. For very odd or intensive sites.

by s9w 10y ago

My neutral (?) view on firefox/chrome: - Firefox uses way less RAM - Chrome is usually faster/smoother, even if not by much. For very odd or intensive sites. And for things like dragging a tab into another window and how long it takes until inspect element loaded. - Firefox has Tree Style Tab, Chrome doesn't and will never have. This alone makes FF the only usable browser for me - I find the non-optional non-native and childish look of chrome silly - Some google sites like the play store and youtube just work better on chrome For me, I use FF because of the memory, the styling and Tree Style Tabs. And I hope they keep on fighting. I understand the chrome users though.

cygned 10y ago
Also using Firefox (Developer Edition) as my primary browser. But my observations are quite different: - On my machine, Firefox uses more RAM than Chrome (Canary) for the same workloads and is slower - Chrome is way faster. As a web application developer I notice that all the time. Chrome renders faster and the JavaScript engine also processes faster. Firefox likes to crash when reloading a page that uses WebSockets. - I don't know your platform, but on OS X the default UI of Firefox is awful. That's the primary reason why I use the Developer Edition.
- NTripleOne 10y ago
  Another thing people don't seem to understand is that Chrome uses as much memory as it sanely can for the task provided. There are situations where it will use more, or less than Firefox, but I guarantee you in 99% of those situations, Chrome will be the one performing faster.
  - seba_dos1 10y ago
    Not true in my case. Chromium often makes the system start feeling unresponsive by causing a lot of swapping, while Firefox deals well with way more tabs open and still keeps some RAM free for other apps to use. When Firefox catches some memory leak and also starts to swap, restarting it fixes the issue (but I have to say that it has become very rare nowadays), but when I restart Chromium, I have to quickly clean up unused tabs to prevent them from eating whole RAM again. On my 8GB RAM machines, Chromium performs faster when there are up to 10 tabs open, but otherwise Firefox easily beats it.
akanet 10y ago
My opposite viewpoint as a web developer: Chrome is faster and renders better than Firefox is pretty much every way. Safari delivers faithful color reproduction and speed. I spent 10x as much time fixing Firefox rendering issues compared to every other browser, including Microsoft Edge. Firefox has lost its edge. I do miss tree style tabs, though.
- chrismorgan 10y ago
  Firefox has been my primary browser since 0.93, so I am naturally biased, but here is my anecdotal position. I develop sites in Firefox and then go for compatibility checking in other browsers. Edge is normally fine. Chrome is horrible. Atrocious. Abysmal. It implements lots of new features, but they are just so regularly buggy or badly implemented. To select the example I remember the clearest (there have been many more over the years): I went to use flexbox on one site and Firefox agreed with the spec (and what was obvious) on the treatment of some major item sizing issue while Chrome did something altogether different which I really couldn’t think of any justification for and which made flexbox a non-starter in that case. A year or two later they had fixed it in Chrome, but I’ve ever found it like that: Firefox has a slower rate of implementation, but normally implements things well; WebKit/Blink has a faster rate of implementation, but breaks things often (even with a handful of serious bugs in production releases that broke entire websites completely) and has always felt like a toy, rather than a serious, stable browser engine.
  - andrewclunn 10y ago
    Try doing flex structures within flex structures in Firefox. Now tell me that Chrome is the buggy one.
  - akanet 10y ago
    I really can't agree - one major area is CSS 3D transforms. Firefox recently broke stacking order (again) context in 3D in the 49 release, and continues to have very poor aliasing artifacts. Chrome/Safari/Edge have pretty solid implementations. Here's just one of the many bugs filed on the topic: https://bugzilla.mozilla.org/show_bug.cgi?id=1187209 https://bugzilla.mozilla.org/show_bug.cgi?id=1187209. Firefox can have major (breaking) paint bugs filed and have "Status: NEW" for basically an entire year.

by s9w 10y ago

cygned 10y ago

Also using Firefox (Developer Edition) as my primary browser. But my observations are quite different: - On my machine, Firefox uses more RAM than Chrome (Canary) for the same workloads and is slower - Chrome is way faster. As a web application developer I notice that all the time. Chrome renders faster and the JavaScript engine also processes faster. Firefox likes to crash when reloading a page that uses WebSockets. - I don't know your platform, but on OS X the default UI of Firefox is awful. That's the primary reason why I use the Developer Edition.

NTripleOne 10y ago
Another thing people don't seem to understand is that Chrome uses as much memory as it sanely can for the task provided. There are situations where it will use more, or less than Firefox, but I guarantee you in 99% of those situations, Chrome will be the one performing faster.
- seba_dos1 10y ago
  Not true in my case. Chromium often makes the system start feeling unresponsive by causing a lot of swapping, while Firefox deals well with way more tabs open and still keeps some RAM free for other apps to use. When Firefox catches some memory leak and also starts to swap, restarting it fixes the issue (but I have to say that it has become very rare nowadays), but when I restart Chromium, I have to quickly clean up unused tabs to prevent them from eating whole RAM again. On my 8GB RAM machines, Chromium performs faster when there are up to 10 tabs open, but otherwise Firefox easily beats it.

akanet 10y ago

My opposite viewpoint as a web developer: Chrome is faster and renders better than Firefox is pretty much every way. Safari delivers faithful color reproduction and speed. I spent 10x as much time fixing Firefox rendering issues compared to every other browser, including Microsoft Edge. Firefox has lost its edge. I do miss tree style tabs, though.

chrismorgan 10y ago
Firefox has been my primary browser since 0.93, so I am naturally biased, but here is my anecdotal position. I develop sites in Firefox and then go for compatibility checking in other browsers. Edge is normally fine. Chrome is horrible. Atrocious. Abysmal. It implements lots of new features, but they are just so regularly buggy or badly implemented. To select the example I remember the clearest (there have been many more over the years): I went to use flexbox on one site and Firefox agreed with the spec (and what was obvious) on the treatment of some major item sizing issue while Chrome did something altogether different which I really couldn’t think of any justification for and which made flexbox a non-starter in that case. A year or two later they had fixed it in Chrome, but I’ve ever found it like that: Firefox has a slower rate of implementation, but normally implements things well; WebKit/Blink has a faster rate of implementation, but breaks things often (even with a handful of serious bugs in production releases that broke entire websites completely) and has always felt like a toy, rather than a serious, stable browser engine.
- andrewclunn 10y ago
  Try doing flex structures within flex structures in Firefox. Now tell me that Chrome is the buggy one.
- akanet 10y ago
  I really can't agree - one major area is CSS 3D transforms. Firefox recently broke stacking order (again) context in 3D in the 49 release, and continues to have very poor aliasing artifacts. Chrome/Safari/Edge have pretty solid implementations. Here's just one of the many bugs filed on the topic: https://bugzilla.mozilla.org/show_bug.cgi?id=1187209 https://bugzilla.mozilla.org/show_bug.cgi?id=1187209. Firefox can have major (breaking) paint bugs filed and have "Status: NEW" for basically an entire year.