So far, any other complexity or augmentation just seems to fall flat in debate.
I have yet to be convinced that this idea is without merit. Mostly, the argument against it goes something like: node reputation is meaningless anyway so this is pointless. My rebuttal goes something along the lines of: node reputation isn't meaningless because we have it and use it; so let's make it more useful. At which point, someone else comes along and says reputation is meaningless anyway so this is pointless.
I've noticed this whole cycle is prevelant throughout the world whenever any change is proposed. Mostly, people just want to maintain the status quo. The naysayers are usually the loudest. However, given the reputation that the original suggestion got and the fact that some of the first replies were supportive, I'd guess there is moderate interest in the idea.1 I think this is indicative of a general feeling that the system should be updated even if ever so slightly, to help enhance its usefulness.
Every thread I've read, and each time I too have tried to think about additional value that might be wrung out of the point/XP system, ends up in a variety of dead ends with more complication than one would want.
Perhaps the authors of those threads didn't have the same ideas, hadn't fleshed them out as well, or couldn't explain them sufficiently. If you want to effectively debate my point, explain to me how this idea results in unwanted complications?
1That's yet another example of using the metainformation contained in the node reputation to draw a meaningful conclusion. Notice that I don't use it in isolation. Also notice that, rather than draw a hard conclusion, I use it to assist me in hazarding a guess.
-sauoq
"My two cents aren't worth a dime.";
-
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.
|
