Live data from Hacker News

Firefox has surpassed Chrome on Speedometer

treeherder.mozilla.org

161–170 of 559 posts

Re: Firefox has surpassed Chrome on Speedometer

#161

Earlier quoted context omitted.

more like vendor lock

"I prefer the way this vendor does things" is not vendor lockin. "I hate the way this vendor does things, but I'm locked in and can't leave" is vendor lockin.

I'd argue that "I prefer the way this vendor does things and I can't leave" is still vendor lock-in. There may be different reasons as to why you can't leave, even if it is just personal preferences.

Google can offer this because you are using a single, fairly unified, ecosystem and they own both your account and browser. However, this ecosystem does not offer interoperability so you are effectively locked-in.

Ironically, this feature is exactly why I can't use Chrome or login on accounts on Android applications: this will auto-sync everything and log you into Google, make logging out very hard, enroll your devices on Google Workspace if that's a professional account, ...

Re: Firefox has surpassed Chrome on Speedometer

#162

Earlier quoted context omitted.

Same. Recently I tried Brave because of all the praise but turns out the browser can only display around 80 tabs on the tab bar and every further tab simply never shows up even if it's in the foreground. I've seen mobile browsers handle many tabs better. I'm staying with Firefox, though I think Brave is probably still a good recommendation for users that don't want to go through the effort of installing an ad blocker…

I'm old and I code for a living, I have maybe at most a dozen tabs open on any day. I can't imagine needing 80 but now I see why chrome has that new search tabs drop down.

On my main Firefox profile I'm rarely below 1000 tabs. I also use them as bookmarks and backlog, and every couple of months I scroll through the entire tab bar and close everything unimportant. The address bar also searches all open tabs and lets me jump to matches.

Re: Firefox has surpassed Chrome on Speedometer

#164
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.

>Firefox's Container Tabs is hard for me to imagine losing. Yes, and the lack of a viable vertical tabs solution for Chrome (though some Chrome based browsers have native implementations). I am baffled how anyone could still be using horizontal tabs as it is clearly inferior. I am also annoyed as hell that it is not native in Firefox.

As a person who habitualy closes everything, I often average around 5 tabs open, rarely going above 10. With so few open at a time, the giant column of vertical space for the tab tree would be a waste of screen real estate, which can be better utilized to open another window i a vertical split arangement, or just for the website's content. Having said that, I know one of my friends has always at minimum 100 tabs open at any time, so he jumped at this feature as soon as ut released. It's a matter of preference I'd say.

Re: Firefox has surpassed Chrome on Speedometer

#165

Earlier quoted context omitted.

I found chrome on macOS to be a sloppy implementation Years ago I remember it was the one app that could reliably kernel panic my MacBook Strange stuff

how the shit does a browser just casually kernel panic the OS ‽ O_o

It was literally the only app that kernel panic'd any of my Macs in years, and it did it repeatedly on a few bad releases across a number of years.

Given the number of devs at GOOG that presumably used Macs, it was astonishing sloppiness to have been let out the door

2012 there was ultimately an Apple driver issue, but only seemed GOOG was impacted / let the code out the door / couldn't be bothered to patch around in meantime https://www.cnet.com/tech/computing/google-yes-chrome-is-cra...

This was not the first or last Chrome MacOS kernel panic. Personally I recall them happening post 2017 as they were happening when I lived in an apartment I moved into around then. Searching around I see references to more of these types of incidents in later years like 2016 & 2019.

Re: Firefox has surpassed Chrome on Speedometer

#166

Earlier quoted context omitted.

which is a fast DNS? 1.1.1.1 ? I thought the OS caches DNS anyway, so shouldn't matter much in day to day browsing.

Anything you can "time nslookup" in or under 0.03 seconds (in "real" terms). From my desk: local one - 0.029 seconds 1.1.1.1 - 0.035 seconds 8.8.8.8 - 0.120 seconds Normally it should be, but Firefox's behavior is very sensitive to DNS response speed. Sounds not intuitive, but I think they're not using glibc's caching, or doing something by themselves.

Curious, where does this number comes from? (0.03 seconds)

Re: Firefox has surpassed Chrome on Speedometer

#167

Does this require some special test environment (special OS, special builds of firefox/chrome)? Because for me chrome vs firefox (both 115) - ubuntu desktop: 148(+-2.2) vs 126(+-6.5) - android phone: 95.8(+-2.0) vs 78.5(+-4.3) So it looks like chrome is faster and delivers a more stable performance while firefox is slower and more inconsistent on performance

I get 260 for chrome & 160 for firefox on win 10.

Re: Firefox has surpassed Chrome on Speedometer

#169

Earlier quoted context omitted.

Really cool how you can see Firefox speed enhancements showing up in discrete steps. I am surprised to see Chrome faster than Chromium. What is google doing in their branded flavor?

On windows you can speed chromium up by renaming it to chrome.exe so it gets special treatment by antivirus software.

Doesn't windows check the signature or something to decide if an application should be allowed to bypass antivirus? Seems like doing it based on the filename would be a pretty huge security hole.

Re: Firefox has surpassed Chrome on Speedometer

#170
post #166

Earlier quoted context omitted.

Anything you can "time nslookup" in or under 0.03 seconds (in "real" terms). From my desk: local one - 0.029 seconds 1.1.1.1 - 0.035 seconds 8.8.8.8 - 0.120 seconds Normally it should be, but Firefox's behavior is very sensitive to DNS response speed. Sounds not intuitive, but I think they're not using glibc's caching, or doing something by themselves.

Curious, where does this number comes from? (0.03 seconds)

Nothing special. Just that if I have a DNS resolving around that timeframe, Firefox becomes noticeably faster.

All of the networks I have have a DNS server around that speed now, and Firefox works visibly faster on all of them. Possibly an intersection between human perception and hardware capabilities of my systems at hand.

Post reply on HN