I'm using Palemoon currently. My understanding is
that PM basically *is* FF, but with a few things left
out that most people won't use. I haven't really tried
to compare the two, though it does seem like PM loads
faster than FF. (Which, of course, is hardly an impressive
feat.) Frankly I don't get the discussions about speed,
x64 optimization, script benchmarking, etc. with a high-
speed connection even bloated pages load almost
instantly. Anyone who can't wait an extra 3/4 of a second
has bigger problems than needing to choose a browser.
To my mind the whole speed issue is just created by the
media to make headlines about a non-existent horserace.
My preference is K-Meleon, which I think of as being
what Firefox is supposed to be: A lean, functional
browser built for people. (MS builds IE for corporations,
Google builds Chrome for Google, Mozilla builds Firefox
for Google, and they all build to serve online corporate
commerce.)
But the K-Meleon project doesn't get much
attention and there are a few functions that I miss when
I use K-Meleon. So lately I've been using Palemoon.
(I'm a bit surprised that there aren't enough idealists
left in the Mozilla fold to break away from the Firefox
fiasco and maintain a single, clean browser project.)
I almost never enable javascript, but on occasion I
visit a site where I decide to enable it. Rather than
switch settings back and forth, I now save Firefox
for the script-enabled sites and use Palemoon for
everything else.
So I like Palemoon but I'm not thrilled. I think FF has
been going in the wrong direction ever since they began
being funded by Google. Since Palemoon is pretty much FF,
it also includes the general bloat, faddism and "corporate
sellout" changes that now characterize FF.
A good example: 3rd-party image blocking. K-Meleon still
has an option in its settings to block 3rd-party images
(which are usually web-beacon ads). Mozilla.org removed
the setting from FF (thus it's missing from Palemoon), claiming
it was "confusing". Not only that -- they also changed
the prefs.js line (about:config) that controls the behavior,
to make it even more difficult to block 3rd party images.
One can still do it, but only Mozilla.org employees and a
few "power users" know about it.
Mozilla.org was getting most of their funding from Google.
Google is Doubleclick. Doubleclick is the biggest operation
online in terms of ads and spying via web beacons. If people
can't block 3rd-party images then there are very, very few
websites where Google can't track a visit. (Even webmasters
who don't use Doubleclick ads or Google Adsense often
add code for Google Analytics because they don't know
how to process their own server logs.) And to be even more
sneaky, Doubleclick and others now often put their ads
inside a superfluous IFRAME, which qualifies the ad as 1st-party,
since an IFRAME is a full-fledged webpage.
All of which means that with 3rd-party ads, script and IFRAMES
enabled, your actions online can be tracked in meticulous detail
by Google/Doubleclick, Microsoft/AQuantive, and various other
targetted ad operations. In other words, Mozilla.org sold out a
long time ago.
--
| Anyone been using the Pale Moon editions of Firefox? It's supposed to be
| more optimized for Windows than standard Firefox, including x64 and SSE
| support available.
|
| The Pale Moon Project homepage
|
http://www.palemoon.org/
|
| Any problems with it that was noticed?
|
| Yousuf Khan