Hacker News new | ask | show | jobs
by Santosh83 3148 days ago
Certainly not the case as far as opening new tabs goes on my machine, an 1.9Ghz with 4Gb RAM. Firefox opens the new tab instantly while Chrome has a noticeable delay. The same with closing tabs, especially heavy ones. Also Chrome takes just a little bit longer to start than the latest Firefox, although I didn't actually measure this.

I think the general perception that Chrome is fast is more a group-think at this point, fostered by a few years of sub-par Firefox performance combined with aggressive Google marketing. There's no real difference since the last few versions of Firefox vs. Chrome.
1 comments
agumonkey 3148 days ago
Trust me, I use "old" core 2 machines, right now on a 1st gen i5 and I regularly cringe at firefox, whenever I run chrome, something lifts off my mind.

I don't charge firefox, it was resetted non long ago, ublock origin and containers (I removed youtube extensions and the likes). Still twitter hungs enough for me to feel annoyed.

I'm not a speed addict, I even love slowness when done right [1], but I rate firefox nightly a little below chrome (stable or canary) at that point.

[1] I use an HP48 calculator, the thing was slower in terms of UI than all its competition but it was such a nice ux design you rarely care about it.

link
terminalcommand 3148 days ago
Did you try firefox quantum? I am also using an "old" machine, first gen i7 mobile processor. Firefox (pre-quantum) was slow for me on windows so I switched to Chrome. But firefox quantum was equally fast if not faster.

Now, I am using firefox 56 on OpenBSD, and it is really really smooth.

link
agumonkey 3148 days ago
I assumed Quantum was in Nightly (58) isn't it ?
link
steveklabnik 3148 days ago
> Nightly (58)

It depends on when you ran nightly; Quantum is the name for 57+. Sounds like you were using it.

link
agumonkey 3148 days ago
That was my understanding too. And as other reported that maybe it was use case dependant, loading imgur front page is harsh, no need for video, webgl or anything too fancy. And of course it's much less the case if at all under chrome.

I wish I had tools and knowledge to analyse the perf/stack locally, really.

link