"freemantle" <
freem...@freemantle.com> wrote
| Firefox locks up where Chrome (I do not like Chrome) does not.
|
| This happens on a Win XP Pro and a Windows 7 PC.
| Latest version for both OS.
|
| The red form close [X] only gives a box that DOES NOT CLOSE Firefox !
| I have to use another program to kill FireFox.
|
I've never seen that happen with either FF or
Pale Moon. Maybe you can provide links to specific
problem webpages. Also, any extensions or plugins
could affect it.
| If I try to post on Mozilla they block this post !
|
The Mozilla groups are mainly run by one Chris Ilias,
who controls it and moderates. He blocks anything
critical. At best you'll be told to post in the "general"
group, which gets no traffic and is mostly just a
junk collector.
I visited the Mozilla groups for awhile but finally
gave up because of the extreme censorship that
blocks even constructive criticism from ever getting
posted. It's a fan club, not a discussion.
That's the nice thing about newsgroups. I find it
odd that more people don't use public newsgroups. They
let Facebook control their lives. They let Reddit require
membership and "vote" their posts up or down. And
in the Mozilla group or Microsoft forums it's similar:
Privately owned, quasi-marketing forums that filter
minority opinions. Yet people somehow prefer that
humiliation to the "public square" of usenet.
| Any solutions, like a better free browser and newsgroup reader ?
I usually check out anything new I hear about.
So far I haven't come across anything promising.
Awhile back this topic came up and I tried one
of the supposedly clean Chrome clones. It tried
to call home. When that was blocked it tried to
call Google. Even SRWare Iron is not clean. I
wouldn't trust anything based on the original
Chromium.
Pale Moon is a lighter version of Firefox. K-Meleon.
also a FF variant, used to be good but has been
neglected for a long time now.
Whatever you use at this point will be some
variant of either Mozilla Firefox or WebKit/Chrome.
If I were you I'd be looking closer at the exact
cause of the freezes. I doubt FF is the culprit.
You might also consider installing the NoScript
extension if you don't already have it. That can not
only help with privacy and security but also greatly
reduce the compexity of pages you visit. Though I'm
not sure about whether it still works in the newer FF
versions. Recent versions now block older extensions
and many of the good ones no longr work.
It's an awkard situation all around. People increasingly
think of the Internet as a shopping mall and
entertainment venue. That means commercialism. That
leads to complex webpage code and lots of spying.
A few years ago, a webpage of 100 KB was too big
to be usable. More recently pages have been 2-3 MB
when all the javascript is counted. Now it's going even
more out of control, with pages of 20 MB not unusual.
Companies can often charge for ads if they autorun
videos, so you can end up with a half dozen videos
playing on a page.
Webpages have become complex software programs
that the browser must compile and run almost instantly.
Browsers are now required to be amazingly fast
and complex programs. It used to be they only had
to calculate the layout of webpage elements. That
was already incredibly complex. These days the
browser is expected to do the same thing from
moment to moment, with webpages that are constantly
changing.
Making matters
worse, most of the people making these software webpages
have no idea what they're doing. They link to javascript
libraries and then go online and collect snippets of
javascript code to add snazzy features to their webpages.
*The webmasters, for the most part, don't understand
the code in the own webpages. They have no inkling
of how it works or even whether it's safe. Much of it isn't.*
But you can simplify things a lot if you use a HOSTS
file to block unnecessary 3rd-parties and either block
javascript or use something like NoScript to reduce it.
If you use NoScript you'll see that most commercial
sites are pulling in script from numerous external
sources. They hand you off to trackers and advertisers,
who hand you off to still more trackers and advertisers.
It gets very complicated. And the browser can stall if
even one of those remote sources doesn't respond quickly.
Yet most webpages that require script will work fine
if you allow only the script that's actually coming from
that domain.
Example: The other day I needed to check
flight status at American Airlines. Like most big sites
these days, their page is a bloated mess of unnecessary
script that's completely, unnecessarily broken if script
is not enabled. Yet the page worked fine when I enabled
only the
aa.com script and blocked all others. What others?
openx.net, an advertising company, and
tiqcdn.com,
a spyware company. Why do I need to be tracked to
check a flight? What are they doing trying to show
me ads? I'm their customer already! If I allowed those
scripts then NoScript would probably show me 4-6 new
sites that wanted to run script.
Long story short, if you put some time into restricting
webpages through HOSTS and script blockers then
you can get much improved security and privacy while
also getting a more stable browser. I rarely see ads and
I rarely visit webpages that don't load almost instantly.
I also almost never see cartoons, slideshows, popups,
or other distracting movement on pages.
These days you
shouldn't allow websites to run script uncontrolled, any
more than you should allow sites to download and run
software on your computer. Because that's exactly what
they're doing. You're not visiting a website. You're
downloading a large, complex software program written
by some kid just out of college who has no understanding
of how that webpage works. He created it using a webpages-
for-dummies program. When he's not on his power
skateboard, going to buy bottled water or a decaf latte,
he's busy chatting with his cohorts, collecting ideas and
links to code and gadgets that will increase the "wow
factor" of his webpage. If any of those gadgets makes
his page hackable and leaves you vulnerable, he'll
probably never know. That's not his job, man. :)