And the devtools are nowhere near comparable to Chrome's, although I admit this might be a matter of personal experience.
That last one was the killer difference for me. Firefox wants me to be able to see (at least part of) the title of each tab, even if that means I can't see all my tabs at once. I want to see all of my tabs at once, and I don't care if I can see the title - the favicon is enough.
I did try configuring Firefox to let me shrink the tabs more, and even tried messing with its GTK configuration, but no luck.
So I do feel a bit bad for using Brave instead of Firefox, but after months of dealing with Firefox's UI I lost patience.
This can be changed via chrome/userChrome.css.
Mine is:
@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");
.tabbrowser-tab {
min-width: 3em !important;
clip-width: 3em !important;
}
[uidensity="compact"]:root {
--tab-min-height: 30px !important;
--newtab-margin: -3px 0 -3px -3px !important;
}
.tabbrowser-tab {
max-height: var(--tab-min-height) !important;
}
.tabs-newtab-button{
margin: var(--newtab-margin) !important;
}While I cannot be sure, I assume that is the cause of the general slowdown I experience as well.
Restarting Firefox will fix free up the memory & fix the slowness. I do still use it as my primary browser despite these issues.
Do note that I regularly have multiple browser windows open (and these are usually on private mode) with 50+ tabs so my usage pattern is not very standard.