In modest defense of updating a node:
It makes sense (after a fashion), in a chatty discussion engine (like, say, NNTP, or fark.com) to disallow the editing of postings after they are committed, for the reasons discussed here. But it often occurs, particularly on USENET, that the thread degenerates into a mob attacking some hapless poster who is unable to change what he wrote.
But is it not more to the purpose of the Monastery that we build a collection of the most useful nodes possible? That end would seem to be better served by correcting and improving the original node in response to the discussion. Of course the editing will always reflect the judgment of the editor, with which there will be, naturally, disagreement. Careful composition of each post so that it stands on its own, and can be understood and judged on its own, will alleviate the dependence upon other posts, reduce the appearance of contentiousness, and create a better, more useful node, all at the same time.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||