> Why are we only attempting to harvest the negative thoughts (with the
> word negative chosen carefully here as voting "No" is seemingly an
> offense to some), why do we not also record why a feature was voted
Well a significant part of the purpose of the RFC is to make the case
for why it *should* be done, and the benefits in doing so, and only to
bring it to vote once the negatives have either been resolved, or are
just down to personal preference.
To vote yes is to state your overall agreement with the arguments made
in the RFC. If you've read up and want to vote "no", I think that is
perfectly fine and should be fully encouraged, but do the decent thing
for your fellow developers and explain why so they're not left trying to
Ultimately, how can an RFC ever be improved to be more widely acceptable
if the people voting in the negative don't give feedback?