You raise an interesting point Dwight. Firstly though, all credit to Mark for setting up the MLO uservoice facility as an interim. Andrey said in the product roadmap that he will be looking at a longer term solution for feature suggestions which may or may not be uservoice. I tend to agree with you that the facility to vote against something is useful (if not abused). Other user voting services like userecho already have this. The advantage, I think is threefold.
Firstly, it helps to avoid feature bloat if a significant number of people do not want a feature. Secondly, if a majority are indifferent to a feature and don't rate it highly enough to vote for it then they should still have the opportunity to lower it's priority i.e. vote against it. If this happened, features that are most important to most people would be developed first. The economists call this "opportunity cost". In this case, with limited resource, the true cost of developing a new feature is what doesn't get developed in it's place. Thirdly, a strong against vote might sway the developer into making a feature optional where possible to keep everybody happy. -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en.
