Comment 18 for bug 290194

>First of all, the fact that there is arguing about this bug in the first place
>shows you that you can't blithely make the claim that it's effectively better
>for most users.

Minority users are especially good at both arguing incessantly and persistently
for their chosen method. Three or four people in a user population of millions
is incredibly insignificant in terms of gauging user response.

If you don't understand why unlimited prefs are bad, you don't have a clue why
the Phoenix project was founded. Most users (generally studies come in around
75%) don't touch prefs, so choosing a default method is key. Supplementary to
that is the fact that supporting multiple methods of sorting/displaying options
is more code. If 50% of the users that even touch prefs (which is certainly a
very high estimate) want alphabetical order, that's still 12.5% of your
userbase. That means 87.5% are paying a price in bloat for a feature they will
never use. That's bloat to most people.

Alphabetical sorting is a terrible concept, and does nothing to adapt, and the
more you visit a site, the more it makes the list unusable. You can argue until
you're blue in the face, but lousy application logic will not go into Firefox,
especially if it adds code.

The more I read of this bug, the closer to WONTFIX it becomes.