I can’t use Palemoon

[fargred]

Sorry for saying that, but I just cannot use Palemoon because it’s a cripple. I’ve found it when Firefox embraced Australis in the late 20’s (or beginning of 30’s?) and back then I thought that it will be a good and clean alternative. I was okay with some add-ons not working or working very unstably, the lack of JIT for user scripts was not hurting my user experience too much, though I was suffering from it every second day. But when today’s update for TreeStyleTab replaced my installed version of 2014 to the more older, from 2013, that just didn’t work properly whatever I could do, this was the end. I cannot deal with 50–100 tabs without TreeStyleTab, hence, I cannot use browser in which it doesn’t work. So I’ve tried to port what I now had in palemoon to chromium, but there were three major flaws and several more minor that made me reconsider the option of using original Firefox. I’ve just copied my palemoon profile to the firefox folder, installed classic theme restorer add-on and replaced adblock latitude with uBlock (that wasn’t available for Palemoon). And you know what? Despite being bloated with Australis, Firefox won by the used RAM size. Also Latest TreeStyleTab wasn’t laggy as it was in Palemoon. This all makes me feel sorry for the time I spent using it.

Here is a screenshot: at the time TreeStyleTabs ultimately broke in Palemoon, I had 72 tabs open in total and 22 pinned. Note that only pinned tabs are actually loaded at the browser startup. After setting up Firefox I was a little curious about how much memory would the new Firefox hog, that is, how much RAM will I be losing abandoning Palemoon. For this purpose I made the tab list correspond to what was opened in Palemoon and restarted both browsers to see the memory. 222 MiB in favour of Firefox. How can that be? I think that’s uBlock for you. Now imagine how much difference it would make on all 72 tabs.

P.S. The addon showing the number of tabs in the bar at the bottom is Vimperator—one of the 17 installed addons (18 for Firefox).

[fargred]

Ah, and anticipating your first question ‘Why wouldn’t you upgrade to 25.4?’—it didn’t work well. Sometimes input fields got blocked by some thing and it required some fiddling with mouse and/or TAB key for it to be working.

[Moonchild]

So, to recap: you're complaining because one of your extensions (which is out of our control) was, probably because of addons.mozilla.org (which is out of our control also) being broken, replaced with a much older version that probably isn't compatible with Pale Moon to begin with, and subsequently broke.

Does that mean Pale Moon "sucks", to put all of your tirade in one word? Or are you jumping the gun?...

I'll let you figure that one out, yourself.

I hope you enjoy Firefox and its increasing reliance on Mozilla Commercialism and third-party services.

[fargred]

So, to recap: you're complaining because one of your extensions (which is out of our control) was, probably because of addons.mozilla.org (which is out of our control also) being broken, replaced with a much older version that probably isn't compatible with Pale Moon to begin with, and subsequently broke.

Yes, this is it.

Does that mean Pale Moon "sucks", to put all of your tirade in one word?

Not exactly this, but this page does https://addons.palemoon.org/resources/incompatible/ Because add-ons are essential for a Firefox fork and breaking compatibility with them means stripping firefox down to some midori-tier browser.

Or are you jumping the gun?...

No, you.

I hope you enjoy Firefox and its increasing reliance on Mozilla Commercialism and third-party services.

My level of freetardness seems very tiny in comparison to that of yours, sensei.

[squarefractal]

Well...
If you are having trouble with Pale Moon...

If you want to huff and puff and switch browser, you are welcome to do so, but please don't give me the arse-end of your mood just because you can.

OP could get the last working version from AMO but I don't understand why they don't want to.

[Axiomatic]

Sorry for saying that, but I just cannot use Palemoon because it’s a cripple.

It is, "Pale Moon" not "Palemoon".

I’ve found it when Firefox embraced Australis in the late 20’s (or beginning of 30’s?) and back then I thought that it will be a good and clean alternative. I was okay with some add-ons not working or working very unstably, the lack of JIT for user scripts was not hurting my user experience too much, though I was suffering from it every second day.

The Mozilla code base is not oh so pretty, you posted a thread asking about JIT for UserScripts here, but you never followed up. Posting it also in the GitHub issue tracker may have helped remedy that suffering.

But when today’s update for TreeStyleTab replaced my installed version of 2014 to the more older, from 2013, that just didn’t work properly whatever I could do, this was the end. I cannot deal with 50–100 tabs without TreeStyleTab, hence, I cannot use browser in which it doesn’t work.

Your problem can be easily fixed. (Why Firefox installed you an older version sound like a bug, perhaps you could have reported it as such? I suspect because of the signing event.)

So I’ve tried to port what I now had in palemoon to chromium, but there were three major flaws and several more minor that made me reconsider the option of using original Firefox. I’ve just copied my palemoon profile to the firefox folder, installed classic theme restorer add-on and replaced adblock latitude with uBlock (that wasn’t available for Palemoon). And you know what? Despite being bloated with Australis, Firefox won by the used RAM size. Also Latest TreeStyleTab wasn’t laggy as it was in Palemoon. This all makes me feel sorry for the time I spent using it.

You may want to reset that profile in Firefox to have default settings, Pale Moon, and Firefox do not share the same settings, and issues can occur because of that.

Here is a screenshot: at the time TreeStyleTabs ultimately broke in Palemoon, I had 72 tabs open in total and 22 pinned. Note that only pinned tabs are actually loaded at the browser startup. After setting up Firefox I was a little curious about how much memory would the new Firefox hog, that is, how much RAM will I be losing abandoning Palemoon. For this purpose I made the tab list correspond to what was opened in Palemoon and restarted both browsers to see the memory. 222 MiB in favour of Firefox. How can that be? I think that’s uBlock for you. Now imagine how much difference it would make on all 72 tabs.

P.S. The addon showing the number of tabs in the bar at the bottom is Vimperator—one of the 17 installed addons (18 for Firefox).

I have a few installed add-ons myself:
2 Pane Bookmarks
BetterPrivacy
chanArk
Clean Links
DOM Inspector
DownThemAll! - should be noted beta 3.5 is what I had installed.
Encrypted Web
Firebug
FlashDisable
How Many Times Can I Back?
NoScript
Pentadactyl
Screengrab (fixed version)
Scriptish
Stylish
Tree Style Tab
uBlock (grab it from the GitHub repository works just like on Firefox for me). https://github.com/chrisaljoudi/uBlock/releases
Zuzpend

The highest I have seen Pale Moon take up is around 770MiB. At the time I was running around 121 tabs (all non-pinned).

So maybe before you accidentally shoot your foot off, try installing uBlock, and the latest version of Tree Style Tab that works with Pale Moon, and see how that goes for you. (TST, has been lagging for me too though, so you are not alone there.) (You may want to update to the latest version of Pale Moon too.)

[Moonchild]

Since the OP doesn't seem to be interested in listening to what is said and would rather just stir things up, I'm not going to partake in this thread any further (also because I don't support Firefox, and porting your profile across from Pale Moon to Firefox isn't supported by me).