So because some programmers aren't bright enough to maintain their code properly (which includes comments), comments aren't as useful?
You misunderstood my point if you think that this is just an issue of programmer intelligence.

Code has an inherent advantage over comments in that it is actually executed, which means that obvious nonsense (eg syntax errors) is caught immediately and massively improves the chance that other errors (eg stupid thinkos of various kinds) are caught as well. Comments don't get this kind of testing, and so lack this valuable feedback.

Can you (with a straight face) seriously make that argument and say the flexibility of Perl is good in the same sentence?
Yes, I can. A standard solution to the issue that I gave above is to design code so that it is, in so far as possible, a comment on itself. Along this line, quite a few of the syntactic constructs in Perl are present explicitly so that you have a choice about how to say things - and can therefore choose the one which will emphasize to another reader what you mean. (I know that Larry thinks this way because his various speeches and Apocalypses have hit directly on this exact point.)

Therefore the flexibility of Perl is good in part because it assists in addressing the issue above about comments.

Obviously if comments are poorly written, and poorly maintained they're not going to help. Same with poorly written and poorly maintained Perl code, but you don't see us stop using Perl do you?
If you fail to understand the intrinsic maintainance issues that comments have, then I can guarantee that your comments will become poorly maintained.

For a more detailed explanations of what I think about commenting, see Re (tilly) 2 (disagree): Another commenting question,. Unfortunately that discussion was carried out half in posts, and half in private chats. The private chats was a more positive conversation, and I regret that the public record that was left is more negative than it needed to be...

In reply to Re: Re: Re: Re: Re**4: Non-English posts on Perlmonks by tilly
in thread Non-English posts on Perlmonks by Vennis

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.