I remember when Mozilla first announced that they would be shifting main focus over to Firefox, and what their core aim with this new browser was:
Firefox is simply smaller, faster, and better – especially better not because it has every conflicting feature wanted by each segment of the Mozilla community, but because it has a strong “add-on” extension mechanism. We recognize that different users need many different features; such demand is legitimate on its face. Attempting to “hardwire” all these features to the integrated application suite is not legitimate; it’s neither technically nor socially scaleable.
It’s been 4 years since then, and Firefox has not become any ‘smaller’ or ‘faster’; ‘better’ being a relative term, depending on what you want from your respective browsers. What’s worse is that there are so many features in the browser out-of-the-box, it ‘feels’ heavier than it actually is. Adding extensions on top of this makes a perfectly good browser behave erratically as far as memory and speed goes. Different test and benchmarks I’ve been following show that 3.0 seems to be even more loaded, albeit not at the cost of speed. That doesn’t make the screams of ‘bloatware’ in my head any softer.
It seems like the pressure to make it ‘just work’, and in their attempt to try and reduce the damage caused by broken extensions, Mozilla has lost it’s focus. Adding features upon features, they’ve managed to make it the biggest necessary evil on any computer.
The same goes for operating systems. I know I have vouched for Vista in the past, but I’ll agree that Microsoft actually has traded performance for features. It might be tremendously secure, and very good looking, but it’s slow; and unless you have the hardware to support it, almost non-functional. Not everyone has a Macbook Pro to to blaze through their work, but let’s be honest, if you did have a Pro you wouldn’t be working on Vista anyway. And why is that? Because Leopard (and Tiger more-so) are easily at the pinnacle of usability today. They’re fast, functional, feature-rich while not being bloated. Sure, the changes aren’t as obvious as they are with Windows releases, but I consider that a positive because it keeps the element of familiarity intact.
Measure of usability
I think it’s wrong to measure the usability of software that comes our way through its features. We should judge it by what it has helped us achieve. How much more productive did it make us. Are the features being touted actually used by the common user? Rather than think of a software as good or bad, we should think in terms of good or bad ‘for us’. If you’re a power user who needs 90% of the features, by all means go ahead and use it. But if you want to use Outlook as a mail-client, then obviously you shouldn’t complain of it being heavy on resources.
The same concept should be aimed at developers as well. Whenever you’re planning the next version of your software, don’t plan as a developer. As programmers, we tend to over think the requirements of the common person. I always say, it takes a child to think like one. Put the common man in your place, and let them decide what they want. All you get to do, is see how feasible it is to include that feature, as compared to the time it’ll take. That way, you’ll save yourself tons of time, and make your user base happy as well. This is one of the reasons open-source software works so well.
At the end of the day, you can’t use a sword to cut a steak, no matter how fancy your sword.

