Pale Moon Fork and Why I Moved To It

I have been using Firefox for a long time – my old laptop has 1.1 on it – and was quite happy with it. I used to post links to it with the caption “Finally, a browser that works the way I want it to!!”
Recently Mozilla has been making changes that made that statement somewhat deceptive though, and a source of increasing frustration/irritation for me and others. [GHacks Article]
I had heard of Pale Moon but I use Linux and it was Windows only at the time. When a member of the community made a Linux version I jumped on it.
I had expected a few bugs since it was a new project but that was not the case as it worked perfectly from the start and I am a happy camper again.
I had been tweaking my profile for years [screenshot] and did not want to lose any of that, but my fears were put to rest as I copied it over with nary a hitch.
The 20 or so extensions I had installed worked as usual with 2 exceptions and one of those (Bamboo Feed Reader) now has a working one in Pale Moon’s own small but growing extension site.
For me it has been stable and very low on memory usage – seldom goes over 300MB.
I am quite relieved and happy that someone came up with this and I recommend it highly.

2 Comments on Pale Moon Fork and Why I Moved To It

  1. Richard Allen | June 23, 2015 at 9:39 AM | Reply

    Glad to see another convert! I haven’t been using FF as long as you have but did start using it when v3 was released. Just recently when v38 was released I decided to move to v31.7 ESR because I got tired of dealing with all the new features. FF has been one of my backups for 3-4 years now since PM became my primary browser on Windows. Definitely a huge fan of PM. The one thing you might want to look at, if it’s in any way a concern, is “browser.cache.compression_level” which is set to 0 in FF but set to 3 in the Windows version of PM, don’t have a clue what it is in the Linux version. I use 0 which seems to speed things up with my hard drive, probably a great option to use with a ssd though. .

    • “thing you might want to look at, if it’s in any way a concern, is “browser.cache.compression_level” which is set to 0 in FF but set to 3 in the Windows version of PM”
      I had changed that to 0 because I don’t have any problem with disk space and like to keep things speedy.
      Probably useful with a ssd as you say.
      A thread on that @ Pale Moon …
      https://forum.palemoon.org/viewtopic.php?t=6831&p=44290

      This is from http://www.tweakguides.com/Firefox_10.html
      browser.cache.compression_level [Integer] – This setting determines whether Firefox compresses the data in the disk cache, reducing the size of it. The default value is 0, which means compression is disabled. A value of 1 to 9 enables compression, with the higher the value, the greater the data is compressed, but the potentially slower browsing may become.

Leave a comment

Your email address will not be published.


*