From an open source perspective this generally works, it will be tested in proportion to the interest in it and if some bugs slip, thats ok. Generally in a commercial culture the more features you have the more of a testing burden you take on to maintain a certain level of quality. Sometimes its less work to go through and remove a feature than to keep it and have to test it.

Also when discussing visible options (rather than hand fiddling with gconf) there is a balancing act with how many to expose and how. We might say "one more might not hurt" but a company needs to continuously balance how many and of what options to expose to keep the options from overwhelming the user. Even in my open source software, if I can't think of a clean way to expose an option than I try and leave it out no matter how many request it.