Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firefox has surpassed Chrome on Speedometer

treeherder.mozilla.org

Post reply on HN
Print view View original

21–30 of 559 posts

Re: Firefox has surpassed Chrome on Speedometer

#21

Post by post-it »

dsauerbrun wrote: post #15
xd1936 wrote: post #8

I've used Firefox as my primary browser since the "Quantum" in 2017. Chrome still feels snappier, but Firefox's Container Tabs is hard for me to imagine losing.

pretty sure chrome has had tab grouping for over a year now

Are they containerized? I have separate containers for work and personal stuff, with separate sessions for Gmail, GitHub, etc.

Re: Firefox has surpassed Chrome on Speedometer

#22

Post by allarm »

dsauerbrun wrote: post #15
xd1936 wrote: post #8

I've used Firefox as my primary browser since the "Quantum" in 2017. Chrome still feels snappier, but Firefox's Container Tabs is hard for me to imagine losing.

pretty sure chrome has had tab grouping for over a year now

That's not what container tabs are. Think of it as isolated environments for groups of sites. You can even set it up so that each new link opens in a new environment, without any cookies, etc.

Re: Firefox has surpassed Chrome on Speedometer

#23

Post by seba_dos1 »

dsauerbrun wrote: post #15
xd1936 wrote: post #8

I've used Firefox as my primary browser since the "Quantum" in 2017. Chrome still feels snappier, but Firefox's Container Tabs is hard for me to imagine losing.

pretty sure chrome has had tab grouping for over a year now

How are tab groups relevant here?

Re: Firefox has surpassed Chrome on Speedometer

#26

Post by bee_rider »

veave wrote: post #3

Is this one of those synthetic benchmarks that don't mean much?

It looks to measure a bunch of little JavaScript-driven interactions. It has been around for a while, so I guess it probably measures what it says it measures.

OTOH, you might feel it doesn’t mean much depending on your priorities. I mean, JavaScript is bad anyway. So I guess anyone they cares about performance/security blocks it as much as possible and/or avoids JavaScript heavy sites.

Or, big picture, Firefox wasn’t built by a spying company, so even if Chrome had much better benchmarks switching to Chrome would be a silly thing to do.

Re: Firefox has surpassed Chrome on Speedometer

#27

Post by haswell »

dsauerbrun wrote: post #15
xd1936 wrote: post #8

I've used Firefox as my primary browser since the "Quantum" in 2017. Chrome still feels snappier, but Firefox's Container Tabs is hard for me to imagine losing.

pretty sure chrome has had tab grouping for over a year now

Container tabs isolate sessions. I don’t think tab grouping is related.

Firefox allows you to create/manage multiple containers, and set up rules to assign specific sites to specific containers if desired.

I think the closest feature in Chrome is the ability to create multiple profiles, but this is less flexible/ergonomic IMO.

Re: Firefox has surpassed Chrome on Speedometer

#28

Post by otabdeveloper4 »

xd1936 wrote: post #8

I've used Firefox as my primary browser since the "Quantum" in 2017. Chrome still feels snappier, but Firefox's Container Tabs is hard for me to imagine losing.

> Chrome still feels snappier

I actually tested this and Firefox is significantly faster in rendering CSS and tables. (Not sure about complex Javascript.)

Chrome's snappiness is mostly UI smoke and mirrors, actual sites load faster for me in Firefox.

Re: Firefox has surpassed Chrome on Speedometer

#30

Post by insanitybit »

otabdeveloper4 wrote: post #28
xd1936 wrote: post #8

I've used Firefox as my primary browser since the "Quantum" in 2017. Chrome still feels snappier, but Firefox's Container Tabs is hard for me to imagine losing.

> Chrome still feels snappier I actually tested this and Firefox is significantly faster in rendering CSS and tables. (Not sure about complex Javascript.) Chrome's snappiness is mostly UI smoke and mirrors, actual sites load faster for me in Firefox.

Maybe FF should take some tips on those UI "smoke and mirrors". What feels faster is what users are going to go off of. For example, a page that fully loads in 1 second vs a page that incrementally loads in 1.5 seconds - the latter may feel faster because the time to start loading is faster.
Post reply on HN