Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

It's different in that

  • it's faster
  • you won't be treading the line of danger with the people who hate "thank-you nodes".

For all that, I tend to agree that a responding node is more appropriate. For one thing, there are frequently several solutions that work; for another, threads often have a fair amount of cross-talk between answers, which will tell you if something's either incredibly brilliant or mind-bogglingly stupid (somebody will presumably have replied to that effect).

And I'm somewhat leery of marking a node as The Answer--if somebody else comes by with the exact same question, they benefit slightly, but somebody with a subtly different problem may read the thread, jump straight to "The Answer", and miss the node down below which warns them about the limitations of this approach (disaster ensues). Granted, that's very hypothetical, but I don't know that it's that far off.

So on the balance, I think this idea sounds good but would have at best a small positive impact--besides, do we want another kind of voting for people to get annoyed about?



If God had meant us to fly, he would *never* have given us the railroads.
    --Michael Flanders


In reply to Re: I'ma getting crotchety in my old age by ChemBoy
in thread RFC: flagging solutions... by suaveant

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 drinking their drinks and smoking their pipes about the Monastery: (3)
As of 2024-03-29 14:38 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found