Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
    Let's give a person who asked a question right to "reject", hide or even delete an answer that he thinks does nothing good to add!

No.

First, this sort of arbitrary re-writing of the Monastery's history is at best ethically questionable. Your suggestion would bypass the consideration system entirely, giving everyone the (somewhat limited, I'll admit) power to silence nodes they don't like, with no accountability. IMHO, that's a very bad idea.

Second, if someone replies to a question with a bad answer, there's always someone willing and able to call them on it. The "bad" answer is flagged, and useful discussion (in the vein of Dominus' Red Flags articles) follows.

Third, not all replies that seem like bad answers to the questioner really are. For instance, the best answer to "how do I parse XML with regexes?" is usually "you don't, use a module instead", which isn't what the questioner wants to hear. I can also imagine situations where the questioner doesn't really know enough about the problem to differentiate good answers from bad.

--
The hell with paco, vote for Erudil!
:wq


In reply to Re: How node in SOPW is answered? I suggest author's ability to reject bad answers by FoxtrotUniform
in thread How node in SOPW is answered? I suggest author's ability to reject bad answers by Chicken

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (3)
As of 2024-03-29 02:30 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found