Floorp, I use it and I love it. It’s especially great for Opera refugees, it has workspaces and stuff. Soon Firefox will support tab groups natively, and then Floorp will be perfect. It’s a Firefox fork though.
Tab groups and non-independent tab muting (seems like it was domain-specific rather than tab-specific last I tried) are the two main things that kept me from switching back to FF as my primary browser (still use it for DTA, for example, but DTA got a big nerf back during the major extension overhaul, so that was a letdown). Tried some extensions, but none really worked in a way I considered usable and didn’t want to just keep trial and erroring through them given I already have a browser that functionally meets my needs, even if I’d rather not be using a chromium browser.
If native tab groups work well enough, I’ll probably give it another chance.
I sometimes just need to mute something for a second that I’m otherwise listening to. Or I’m switching between multiple sources, and don’t want like 3 or more playing at the same time… usually all on the same domain. I don’t want to have to actually go to the tab and mute it. I’m frequently muting and unmuting things that way to the point that even if its the only source of sound, I still mute by tab instead of just turning my computer volume off sometimes out of habit, so its a deal breaker.
I think this just says more about the perils of embracing untreated ADHD than the internet itself.
you may not even have to change to another browser or fork, please have a look at some designs in trickypr.github.io/FirefoxCSS-Store.github.io/select a design and follow the page, and you shall find the instructions (usually just downloading/pasting userChrome/Content.css)
and for scrolling tabs, if your problem is very small tab size, then try changing browser.tabs.tabMinWidth in about:config
They used to also use the unreleased version 0 of shadow DOM for building the Polymer UI, which - being a Chrome-only prototype - understandably didn’t work on Firefox, and therefore instead used a really slow Javascript polyfill to render its UI.
I haven’t checked on it lately, but I imagine they must’ve changed at least that by now.
That's a really weird take. Like… what even is the difference supposed to be?
This sounds more like “everything should be as it was back when <insert arbitrary point in time here>! When there were still Webpages, and we were frolicking about the internet! Until the fire nation attacked Web apps took over!”
In general, browser benchmarks seem to often favor Firefox in terms of startup and first interaction timings, and often favor Chrome when it comes to crunching large amounts of data through JavaScript.
I.e. for pages which use small amounts of JavaScript, but call into it quickly after loading, Firefox tends to come out on top. But for pages which load lots of JavaScript and then run it constantly, Chrome tends to come out on top.
We’re usually talking milliseconds-level of difference here though. So if you’re using a mobile browser or a low-power laptop, then the difference is often not measurable at all, unless the page is specifically optimized for one or the other.
Ironically I use a chrome type browser for YouTube and mail checking only. This is also the only browser in which I am logged in with my Google account.
My main Firefox is for everything else including search.
One thing you can test is to apply a Chrome user-agent on Firefox when visiting YouTube. In my personal experience that actually noticeably improves the situation.
There’s a bunch of extensions that allow you to switch user-agent easily, I personally use this one, it includes a list of known strings to choose between as well.
You haven’t experienced slow until you try to take Firefox through Google Cloud Console or Search Tools. 15 seconds in Chrome, somehow turns into 3 minutes in Firefox, funny how it does that.
Google does that a lot with their own web properties. I remember Google Meet didn’t support background replacement on Firefox, but switching Firefox’s user agent to Chrome suddenly fixed it.
I remember when Chrome was released, all marketing was on how much faster it rendered webpages, I never saw that as an issue, Firefox was fast enough, I tried Chrome for a bit, and hated the UI, I remember being confused as to why everyone loved Chrome suddenly, and frankly, I still am a bit confused by both the sudden shift, and the absolute market dominance by Chrome…
I hated Chrome’s UI so much that I switched from Firefox to Pale Moon when Firefox started the whole Australis design language, and only switched back when the current design was launched
I grew up with a 56k modem. Anything after adsl is warp speed for me. I never understood or observed the speed differences between browsers.
Maybe I’m just so slow myself that I dont notice the difference but come on… how much can it be? A few seconds? Who is so busy that a few seconds is a worthy amount of time to try and save (not talking about F1 drivers here)?
I switched from FFX to Chrome back in the day because Chrome tabs were all independent processes in task manager, and one crappy website wouldn’t kill my whole browser.
When Google started their war on addons, I switched back to Firefox.
memes
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.