Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="mamba" data-source="post: 9064053" data-attributes="member: 7034611">I purposely did not say anything about what changes they should make, because I do not want to equate the two issues. I know not everyone agrees, that is obvious.I am also more self-aware and flexible than you give me credit for here <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f609.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=";)" title="Wink    ;)"  data-smilie="2"data-shortname=";)" /> I argue for my preferred solution, sure, that does not mean it is the only acceptable outcome.I still think going by whatever 70% find acceptable is a bad way to innovate, regardless of what changes breaking this rule would bring.One thing this rule does is stifle innovation and actual changes, that much is clear. I’d rather see them do that, regardless of what changes it results in.I grant you that most of those they tried and threw out, I actually liked, but my main gripe with the 70% doctrine is how it does stifle change. I much rather see them have a good solution to a problem, even if it is not my preferred one, than for them to simply not address the problem.The one case where I actually pushed back on it and said that the 70% is outright bad is that it grandfathers in solutions we have but never got 70% approval to begin with, instead of allowing the actually more popular solution of the two to be used, even when neither reaches 70%.Even if you want whatever is the more popular, all of the time, that to me is something you should be able to agree with.The other times I was disappointed that when something did not get 70%, that they abandoned it right away, instead of revising it and trying again. That too should not be all that controversial.As to wanting a solution more than wanting ‘my’ solution, take the discrepancy between SR and LR classes. My fix is throwing out SR as a recharge mechanic. I’d still rather harmonize the classes to all benefit about equally from SRs and generally reduce the dependency on them than keep a mix, like they do.Either solution is better than not addressing the issue, yet the latter is what we get.</blockquote>

Verification