Software Feature Bloat

I'm sure we know by now that more features doesn't better. Depends on the use case

I came here to say this. It does not make sense to add bloated features that are not essential to everyone's use case.

I don't think the problem is the number of features really but maintaining the simplicity or ability to access the features you need. For any given product there are probably a core set of features that everyone wants and beyond that each additional feature pleases some other slice of the customer group but before you add that extra feature you should probably consider what that might cost you in terms of maintaining the simplicity of access and ease of use of your core features.

Features are not bloat if they address real issues.

Exactly. More Features != Better Product.

Different people want different features. There's no way they're going to remain minimal and please everyone.They have to choose the feature set, and if other programs can provide a feature that some users want, that seems like a feature ripe for pruning. I think they made the right choice.

You can't win. Most features added is because someone wants them. One person's bloat is another person's long sought feature.Like a quote about Microsoft Office: A user only ever uses about 10 percent of the features. The problem is that all users use different 10 percents.

It's not about the lack of features. It's about the features that fit 90% of the use cases (sometimes 95%, sometimes 99%, etc), without the software being bloated.

For me having too many features IS a misfeature.

It seems like adding features often reduces functionality or utility.