Live data from Hacker News

Firefox has surpassed Chrome on Speedometer

treeherder.mozilla.org

381–390 of 559 posts

Re: Firefox has surpassed Chrome on Speedometer

#381

Earlier quoted context omitted.

The thing that I really like in Chrome (which I use for work) is Tab Groups. There is nothing like it for Firefox. Even the "Simple Tab Groups" extension, which is well liked, cannot do the simple "grouping" of tabs in a larger window - it simply hides all the tabs that are not in current use (which defeats the purpose of tab groups, I can just use windows for that). Another thing that Chrome has is the ability to na…

Use Sidebery in Firefox for vertical tabs and it has not only better grouping but also entire "tab spaces" (workspaces) which you can switch between as well, if wanted.

How does Sidebery compare to Tree Style Tab?

Re: Firefox has surpassed Chrome on Speedometer

#384

There was a time when Firefox felt a lot slower than Chromium, but for a few years now it's been close enough (even if still somewhat slower) to not bother me, while Firefox clearly offers superior functionality and much better performance under high load. The last time Chromium has felt attractive compared to Firefox was a really long time ago. Glad to see it moving in the right direction still.

I also like that Firefox isn't putting artificial limitations on the plugins that we can use in order to appease their infinite hunger for ad revenue.

Chrome's manifest v3's entire purpose for existence is to ultimately snuff out ad blockers so they can make the internet worse for everyone and get more money in the process.

And if you don't believe me then you are wrong.

Of course they won't do it immediately. They won't entirely rug pull their browser's user base.

They'll just keep raising the bar to get approved for Chrome Store, making it harder and harder to comply with their extension requirements while also changing the way they deliver their ads.

This way the ad blockers have to be updated and then go back through the extension store review process until the developers either get tired of jumping through their hoops and gives up or until they can no longer afford to keep the extension alive.

And then they'll rug pull, just like Reddit and Twitter, and all of a sudden ad blocking extensions will require that the users pay Google for the privilege of having fewer ads while still letting some ads through anyway, and that will be that.

Best to jump ship now, things are nice and cozy over here in "user wants are respected within reason" land.

Re: Firefox has surpassed Chrome on Speedometer

#386

Earlier quoted context omitted.

It's just ADHD, there's not really a workflow reason that I have 1000+ tabs open. It just kind of happens. Firefox/Sideberry is useful for mitigating that. I also have workflows set up for mass-exporting my tabs from Firefox to a text file and reorganizing them in plain-text and re-opening just the tabs I care about[0]. Bookmarking on any browser is cumbersome and leads to disorganization over time. Tree-style tabs h…

It's ADHD sure, but it's also an unwillingness to close tabs, and (generally) that we have poor windowing systems that force us into ~1-2 browser windows at a time because browser windows are harder to manage than tabs. The big change for me has been realizing that all my "tabs" are still there, in the form of my browser history, or if not, via Google search. If I can't find my way back to a website via my history or…

I stopped using persistent browser history because I realized without it I become more diligent at bookmarking pages. Deliberately bookmarked pages are alot less clutter than my entire browsing history, so with my address bar only searching my bookmarks and current session's history, it's easier for me to find what I'm looking for. It results in smaller haystacks for my needles to get lost in. I loath using general purpose search engines to pull up pages when I already know what page I'm trying to get to, so I bookmark any page I think I'll care about in the future.

Re: Firefox has surpassed Chrome on Speedometer

#387

Earlier quoted context omitted.

It's just ADHD, there's not really a workflow reason that I have 1000+ tabs open. It just kind of happens. Firefox/Sideberry is useful for mitigating that. I also have workflows set up for mass-exporting my tabs from Firefox to a text file and reorganizing them in plain-text and re-opening just the tabs I care about[0]. Bookmarking on any browser is cumbersome and leads to disorganization over time. Tree-style tabs h…

It's ADHD sure, but it's also an unwillingness to close tabs, and (generally) that we have poor windowing systems that force us into ~1-2 browser windows at a time because browser windows are harder to manage than tabs. The big change for me has been realizing that all my "tabs" are still there, in the form of my browser history, or if not, via Google search. If I can't find my way back to a website via my history or…

Most of the times when I've tried finding stuff in (Firefox) history, I wasn't able to. Unless it's in the last week or so. In my experience, history filtering and search options are too basic to be useful. Once I was even desperate enough to try to load some Firefox sqlite file directly, hoping to query history entries, but that didn't work out.

The only reliable way that I've come across for finding stuff after a long time has passed is saving every sightly interesting webpage to Zotero and using fulltext search afterwards (including webpage body).

I'm curious, do you find the builtin browser history facilities sufficient for your needs, or are you using some third party tool for that?

Re: Firefox has surpassed Chrome on Speedometer

#388
post #66

Earlier quoted context omitted.

I use it, but just don't like the devtools. Or moreso miss some things from Chrome/Edge.

For me it's the opposite. Firefox's dev tools feel better. What things are missing?

What cripples FF DevTools for me is being unable to find the setting for timeout on HTTP GET, during full-stack development. If I've set a breakpoint in a debugger on my server and proceed to single-step there, FF aborts the GET request with an error. So client-side JS doesn't see the eventual result of the GET, it has to recover from the error to proceed, e.g. by a full page-reload.

Chromium, last I tried it, by default sets the necessary HTTP timeout(s) to infinity if its DevTools is open.

My searches of Firefox docs/wiki, StackExchange, HN Algolia for a fix have come up empty.

Navigating to "about:config" and searching for "timeout" finds 27 different settings prefixed with the substring "network". Some are obviously in units of milliseconds, others perhaps whole seconds.

Anyone know which one (or what combination) might incant the necessary black magic?

Re: Firefox has surpassed Chrome on Speedometer

#389

There was a time when Firefox felt a lot slower than Chromium, but for a few years now it's been close enough (even if still somewhat slower) to not bother me, while Firefox clearly offers superior functionality and much better performance under high load. The last time Chromium has felt attractive compared to Firefox was a really long time ago. Glad to see it moving in the right direction still.

I switched to Firefox from Chrome years ago because Chrome was slower. Specially, when there were many tabs opened, switching tabs in Chrome were usually prefaced with a blank white screen for about 2 seconds. I've been staying with Firefox not for the performance (today Chrome loads Google sites like YouTube faster), but mainly for Tree Style Tab extension. I couldn't imagine opening more than a dozen of tabs withou…

I've stayed (edit: with Firefox) because of (1) containers and (2) password storage. I have to use Chrome for some things, and every now and then it prompts me for a password and refuses to use the auto-fill. Totally torques me off because my passwords are not easy.

But I completely trust Firefox on the password issue, to the point that I let it generate them for me.

Re: Firefox has surpassed Chrome on Speedometer

#390
post #286

Earlier quoted context omitted.

The thing that I really like in Chrome (which I use for work) is Tab Groups. There is nothing like it for Firefox. Even the "Simple Tab Groups" extension, which is well liked, cannot do the simple "grouping" of tabs in a larger window - it simply hides all the tabs that are not in current use (which defeats the purpose of tab groups, I can just use windows for that). Another thing that Chrome has is the ability to na…

Honestly you are the first person I’ve ever heard that prefers chromes tab system. Check out tree style tabs it’ll change your life. I hate chrome now solely due to it

Tab groups in Chrome are a relatively new feature (and might still be behind an experimental feature flag, or at least the ability to save tab groups might be).

They're a game changer; so much better than using a third party extension IMO.

Post reply on HN