comment on

I can remember quite a few occasions where the highest rep answer wasn't the most useful one for the problem I searched for

And you remember few occasions where the most quickly posted answer wasn't the most useful one for the problem you searched for? Otherwise, you present the weakest of arguments against the proposal.

So, add to that "I don't want to use that configuration", which is not an argument against it since registered users have had the option to choose from several configurations for a decade already. Also, one downvote lacking any accompanying explanation.

I think the arguments "for" are winning rather decisively, despite their quite modest showing.

- tye

In reply to Re^11: And here's why I think "downvotes" should be eliminated, or tabulated separately ... (node order) by tye
in thread And here's why I think "downvotes" should be eliminated, or tabulated separately ... by sundialsvc4

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks