Anyone else noticed how fast version 148 was only for the whole speed improvement to go away in 149?
2026-04-16_14-56-30.jpg
2026-04-16_14-52-51.jpg
2026-04-16_14-50-36.jpg
I wonder if you could test alpha 149 builds to figure out where this dip occur ed. Could fix the issue in r3dfox.
https://ftp.mozilla.org/pub/firefox/nightly/2026/01/
https://ftp.mozilla.org/pub/firefox/nightly/2026/02/
In case you missed it (because I "talk a lot", lol), MV3 is *one of the reasons* that I *hate* uBO force-included in recent 'fox forks.
Although, yeah, I probably (probably) shouldn't complain about that UNTIL (it will happen eventually, IMO) Firefox/Forks no longer support MV2.
I *intentionally* use a MV2 version of uBO.
The version included in r3dfox and in the Firefox addon store is MV2 though. There is a uBO Lite that is MV3, and from what I've heard it works pretty well and can even be better than MV2 uBO, but I haven't tried it.
Some people like uMatrix over uBlock Origin for instance
Those are two different types of addons. uMatrix is not the same sort of content blocker as uBlock Origin. They're kinda made to be used together, which I do.
And H#LL YEAH, CNN *and* Fox! When I tell you I am "purple" and a "centrist", I really am.
I HATE THE "EXTREMISTS" ON BOTH SIDES !!!
Corporate controlled opposition *and* literally argued in court that they were not news and just entertainment, and argued that no sane person would take them seriously. You could do a lot better.
- Renders fonts in a way that don't make my eyes bleed.
- Doesn't randomly crash, lag spike or memory leak.
- Doesn't have random issues with certain extensions.
- Performs well while not being a resource hog.
Yeah all that comes from needing to parse the modern internet. I don't think we will ever get that.
However for fonts I would like to bring back Cairo and GDI to r3dfox. However WebRender is a shit, and I did try seeing how well the Basic compositor in 91 fares with Cairo, but it doesn't fare very well. I'd need to fix GDI in WebRender somehow.
The UI of Mypal bugs the crap out of me. Not even sure "why", to be honest.
It's some form of "beauty is in the eye of the beholder" and I just find it and those like it UGLY.
Out of the last three major Firefox redesigns, I prefer the Firefox 68 style the most imo. Although it's a low bar and only beats Austrailous or whatever because the tab shape isn't horrible. 89+ I hate the floating tabs and the line icons are worse, but not worse enough for me to replace them in r3dfox. Except for where it makes the downloads list horrible to check for failed downloads.
If I were to make a Mypal68 fork I'd bring a similar tab design to r3dfox, but it would be near the same for the most part, idk if I would change very much with it.
Was it the death of Presto? Trident? I know Firefox kept getting worse. Modern Firefox is so bad that when I used it recently on another laptop with 4 GB of RAM, the tab would crash on me literally every 5 min. That was with mere 3 tabs at most.
That seems like a weird RAM leak. I didn't encounter this when I tested Librewolf on my T52 with 1GB. It was just very slow, even when I accidentally ran it without a page file. Although that was on x86 Debian Linux.
Pale Moon inherited everything from when Firefox started going downhill...lag spikes, memory leaks...and adds its own issues on top.
Combination of modern internet being awful and them forking at literally the worst point. Firefox 52 was basically the end point where Firefox consistently got slower and slower every release. I feel the browser would've been better off had they just kept extending the 38 ESR codebase. Although you could still do better.
Forks are more or less irrelevant to me as they copy-paste all the bad stuff.
So what do I do? As it is, I just suffer with Pale Moon as I wait for the better browser that will never come.
Next version of Lun3r will come with Dactyloidae's performance improvements, and if things go well, both browsers should merge, so updates should be at least a little more consistent.
Going from the point before, someone should retest the Firefox ESR performance from the beginning to current day. It would be interesting to see how it changed over time. Then test alpha builds to see where the speed decreases or increases came from, maybe those could be fixed in the fork.