Firefox/Thunderbird Plugins: Is Less More? 457
comforteagle writes "I've published the first of a two part look at the new dynamic duo of Mozilla's Firefox and Thunderbird. While most folks thus far agree with the 'less is more' mantra when it comes to the base applications, the plugins seem to be a different story. Hey, there's little wiggle room to debate that the firefox base application (the subject of the first article) isn't the shizzle, but how about the add-ons and plugins? For that matter, do you agree that less is more. or is too little included?"
blah (Score:1, Insightful)
I don't want to view your crappy ads (Score:3, Insightful)
Less is the opposite of more (Score:4, Insightful)
I really like the idea of being able to customize my browser to work just the way I want it to. And being able to pick and choose my plugins with Firefox gives me exactly that. I don't want ALL that junk thrown in! Just a few things, like Adblock, Session Saver, TinyURL Creator, User Agent Switcher and Firesomething (for fun).
Posted from Mozilla Spacemonkey
Depends (Score:3, Insightful)
Myself I prefer absolutely nothing tacked on to my default installation other than the advertised purpose. If I want to add functionality, I'll go looking then.
If you're catering to the masses (ooh look shiny!) then you'll probably have to strike a balance and include the popular functions while leaving the cosmetic or trivial ones to be added in later.
There is no clear cut answer.
I Wish Moz Would Rely a Little Less on Plugins (Score:5, Insightful)
sure, less is more (Score:3, Insightful)
Barebones and plugins = good (Score:3, Insightful)
Less is more - to a typical end user (Score:4, Insightful)
When dealing with Slashdot style users plugins become huge, I like to customize my browser to fit my browsing style and want to see all the options, not what would be best for the typical end user.
To paraphrase Father Mulcahey: (Score:2, Insightful)
KFG
Re:Google Bar (Score:3, Insightful)
Minimalistic and Modular design makes more sense (Score:4, Insightful)
Obvious (and not so) Features (Score:5, Insightful)
When she suggested it to her friend, we ended up with a small laundry list of extensions we like and would suggest. And then I realized - the Firefox that I've come to like is not the Firefox everyone else likes.
Just like any desktop environment I've ever used. If I spend a reasonable amount of time on any system, there are key applications that I must have. Applications that not everyone wants / needs. My desktop environment always looks and behaves very differently than others (how do people work with default environments anyway?).
Maybe this is a reflection of the whole "XUL is a platform" thing. In any case, it is boon and bane. It shows versitility. But it can be a bit daunting to the hapless friend who gets "try Firefox! Oh... and the Widget extension! Oh. And you've got to load up the FooBar too!..."
Re:Thunder/Firebird aren't "less" (Score:3, Insightful)
What I'd like to see is more plugins from the Mozilla developers, it's my understanding that most plugins are not officially supported and are run-at-your-own-risk. Would be nice to have a base browser and some simple plugins that are officially supported and bug tested by mozilla. I for one, cannot live w/out the tabbrowser extensions which just add more functionality to how tabs are used (including the ability to unclose a window which is a memory hog but wonderful when i accidently hit x)
Isn't this how IE goes bad most of the time? (Score:2, Insightful)
Let's hope FireFox doesn't go down that path.
Tabbrowser extensions (Score:3, Insightful)
Then there's Adblock, Zoom Image for those who need it (wink wink), but seriously, this is very helpful for working on a 1920x1200 screen.
I am recommending firefox to everybody I know and have so far successfully converted my whole family and at least two thirds of my colleagues.
benefit? (Score:3, Insightful)
Really for the average user who might use both clients it's just better to run mozilla instead.
As for "how many features to include" honestly I think firefox is too big as it is. If it's *just* a web browser it ought to be smaller and take less ram. But it doesn't.
Though I think people miss the point of firefox. It's not meant to be smaller. It's meant to show off the leading edge. Though honestly most new features aren't that keen to be worth it.
Tom
Multiple 'versions' (Score:4, Insightful)
Alternatively, as long as the plugin mechanism is relatively simply (which it is), and as seemless as possible (getting close), then i dont think there should be a problem for most users to upgrade.
Compare with Internet Explorer, which comes with no plugins, Firefox users are no worse off. Granted, in comparison to maybe Opera, we dont get mouse gestures and other funky things as default.
I guess its a hard thing to decide simplicity/speed vs user base/catchment area. Thus why the minimal/standard installations could be a good idea.
Re:Google Bar (Score:4, Insightful)
Pros and cons about plugins in my opinion (Score:5, Insightful)
1. They leave out reasons for bugs and security holes from the main application since it becomes less complex. Core application developers can focus on just that -- developing the core application.
2. They let users get exactly what features they want so they can customize the application better for their needs. It will become easier to use for this reason (no need to navigate through big menu hierarchies and can spend less time learning how to use the applcation, etc).
3. The plugins, on the other hand, will be developed by highly motivated individuals or groups, which often results in a work of higher quality and better specialized for the job than if it would've been part of the main application and given only the necessary time so the main developers wouldn't delay main application releases. Take the adblock plugin for Mozilla as an example with advanced pattern matching and Flash blocking with content being intercepted before it's downloaded (as opposed to with adblocking proxies that analyze and filters already downloaded data). Or the SmoothWheel plugin that contains a dozen settings to let the user control exactly how the smooth algorithm should work (who can of course stick with defaults and never give it more thought too).
The major downsides are probably:
1. Users need to spend time downloading and finding out if plugins exist for their needs.
2. Users need to keep up to date with more than the main application if the plugins contain bugs he/she wish to see fixed.
3. Inexperienced users who aren't used to plugins, users with a lack of patience, or users who don't want to spend time to tinker with their application to get the features they need might be put off by the lack of features in the main application and switch to another one that's advertised having a larger feature set.
Thunderbird annoyance (Score:2, Insightful)
For example, in Thunderbird there still is no way to just receive plain text email without markup of some sort. (Unless you like clicking on View->Message Source for every message.) *text* renders as *text*, text it detects as sigs is grayed out (even in multiple part digest form messages, rendering half a message as gray!, the > quotation is replaced by a graphical |... and there are probably other changes I have forgotten. Even altering my user.js conf file hasn't completely rid me of the above markup.
It's a good mail application, but any mail program's first priority should be display the email as received. After that, start adding markup.
Re:I'm sorry... (Score:2, Insightful)
Actually the biggest downside (Score:3, Insightful)
Or flash-click, that'll not only play the one you clicked on, but insert a little ad before and after. And so on. ActiveX = plug-ins is the single biggest source of problems on IE. And most of the time, because the users are "willingly" installing it.
Kjella
Re:Depends (Score:2, Insightful)
Re:Speaking of the download manager (Score:3, Insightful)
Re:I like the simple but expandable model (Score:4, Insightful)
A drone will repeat the same task over and over because that's "what they do." A very lazy programmer will get sick of the task after about two iterations and say, "I could replace this stupidity with a small program." A lazy programmer actually writes the code. Of course, some of us spend more hours developing code than will ever actually be saved by using the shortcut, but hey, the risk goes with the task.
And if it's really cool, you share it with friends who all say "ooo, ahh, cool." And then your friends say "hey, can you make it do X, too?" and "hey, neat, can it do Y?" So you improve it.
And then it becomes Mozilla, and you end up splitting off the browser function as a standalone app because Mozilla does too much X and Y...