Mozilla To Enable Click-To-Play For All Firefox Plugins By Default
An anonymous reader writes "Mozilla on Tuesday announced a massive change to the way it loads third-party plugins in Firefox. The company plans to enable Click to Play for all versions of all plugins, except the latest release of Flash. This essentially means Firefox will soon only load third-party plugins when users click to interact with the plugin. Currently, Firefox automatically loads any plugin requested by a website, unless Mozilla has blocked it for security reasons (such as for old versions of Java, Silverlight, and Flash)."
Subject says it all... why enable flash by default? Even if it didn't have any security holes, it's still the great battery eater...
I apologize for the lack of a signature.
I found it Reading the Fucking Article:
Emphasis mine.
"Follow the money." That's a reason I can understand.
Makes me glad I usually run with Adblock and NoScript.
Welcome to the Panopticon. Used to be a prison, now it's your home.
While we as technical users might enjoy a plugin-free experience with no extra clicking involved, the average Joe User is going to be pissed off.
I run with NoScript - does pretty much what Mozilla wants to do (plus script blocking), except without the big gray box. The average user is not interested in NoScript type functionality - they want a rich web experience out of the box, and if that includes Flash, PDF files, and audio, then that's what they want.
I suspect the reason Flash is turned on isn't because of ads - it's because there are a number of high profile corporate websites out there that become unusable if Flash isn't enabled.
Let us live so that when we come to die, even the undertaker will be sorry -- Mark Twain
What will I do with the excess memory if plugin-container.exe doesn't get out of hand anymore? Or perhaps we'll see a new big process: plugin-container-container
I stopped using it because it was so much slower than Chrome at some basic tasks
Are you a "high speed" trader?
What real useful difference does it make? Seriously?
Step 1: Crippling addiction to absorbing information from the internet at all times.
Step 2: Run out of information to absorb from familiar places.
Step 3: Boredom.
Step 4: Find new place from which information can be absorbed. That new place discusses application speed and responsiveness with nanosecond resolution.
Step 5: Absorbed information must be used! Develop brand new crippling addiction of obsessing over browser speed.
Step 6: ???
Step 7: Gain attention by complaining on public forums! Which is a form of profit.
Chrome is really fast. It does stand out when you use it, even if I prefer to use Firefox.
I use both daily and frankly can't really see any speed difference for anything I need to do. While there probably are some differences I'm usually more limited by the speed of my connection to the ISP than anything else.
Chrome uses a massive amount of RAM. About 3x more than Firefox. It is good if you have a lot of RAM but can even run poorly on 8 GB systems, such as if you have virtual memory disabled because of a SSD. I switched back to Firefox because of this.
I can make pixel perfect feature rich cross-platform native application for Linux, Win, BSD, OSX, Android, iOS in 1/3rd the time it takes me to ensure the same "web app" works in all the browsers and OSs.
I want whatever development tool chain you're using. Just dealing with the different installer mechanisms on those platforms makes my head spin. What's your secret?