Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

    On my machine, I can’t even launch Firefox in 
    headless mode without the fans turning on, which 
    never happened on Chrome. While I haven’t benchmarked
    it, for normal browsing it does feel slower than Crome.
I believe you, but I'm always so confused by hearing this. I use my Mac (2015 MBP) 10+ hours a day, evenly split between FF and Chrome.

Truly is close to an even 50/50 split -- FF is my personal browser and I use Chrome for all work-related tasks.

And they are subjectively indistinguishable in terms of performance. The only exceptions to that statement are, well, Google properties where Google has clearly invested time and money into optimizing things for FF.

One other possible sorta-exception is when I'm using a scaled resolution mode on an external 4K monitor. MacOS warns me, straight up, that these modes will cause performance issues for me and my modest Intel Iris graphics. The whole system's a little sluggish in those modes, and I think FF fares worse than Chrome, but I won't hold that against FF.

FWIW, Safari does feel subjectively more responsive to me when it comes to scrolling and navigating. And I recently spent a few bucks upgrading my PC gaming rig to a 120hz monitor, which makes a massive difference. And I'm one of those weirdos who keeps CRTs around for his old consoles because he enjoys that true zero lag experience. So I am not exactly insensitive to latency. I don't have magic professional gamer golden magic eyes or anything, but it is an area of interest for me.



Too late to edit my post, but "where Google has clearly invested time and money into optimizing things for FF" should read "where Google has clearly invested time and money into optimizing things for Chrome."

Sorry.


Makes more sense :-)

Personally I feel it is worse than that: there have been som issues so bad that I hardly get Hanlons razor to work at all, notably one where just having a search result page open in Firefox would consistently spin up my CPU for no good reason twice a minute.

(Of course there were a number of other weird lagging issues as well.)


I think one problem, especially if you have many tabs open, is that about:performance isn't very useful / accurate (at least for me) so I'm not sure which is the offending tab to close. With Chrome that is pretty easy.


When you find the culprits on FF, what do they tend to be? How many tabs do you typically have open? Do you run an ad blocker? Not saying you're doing anything wrong - just genuinely curious about which usage patterns trigger FF to be "slow."

I usually have perhaps 5-15 tabs open in FF and I've really never had a reason to even look at about:performance.

But, I do understand that different people have different usage patterns. I run an ad-blocker and I don't typically have any "heavy" resource-sucking tabs open. Hacker News, old Reddit, Twitter, Wikipedia, NYT, etc. That kind of thing. Not heavy video/streaming/interactive stuff.

Anecdotally my understanding is that really heavy tab users (like many dozens or even hundreds of tabs) feel/felt that Chrome handed that better than FF.


Since you use both Chrome and Firefox, do you know if it's possible to import saved passwords from Chrome into FF on Mac? I was able to do it on my work PC but the Mac version of FF didn't show that option.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: