I strongly think not, and that is a gripe of mine.

Don't get me wrong. I use comments, and on the whole I have quite a few of them. But to me comments are something which has to be done right or else it is worse than useless, and I would prefer to see completely uncommented code to overly verbosely commented code.

For a thread that outlines my personal commenting style and the reasons for it at some length, I would suggest reading Re (tilly) 2 (disagree): Another commenting question,. (Note that behind the scenes we traded a series of /msgs that were more friendly than the discussion there.) After reading that, if you think that I really need more comments than I use, or that my points about how comments can be a problem are off-target, please give me feedback.

I beg to disagree with the statement "The more comments the better.".
Personally I state and restate:
"Any programmer of the language in question is supposed to understand what the code does."
"OTOH, you must document why the code does it."

This is especially important when the code makes assumption about the behaviour of external libraries or when the code depends on (more or less documented) side effects.

f--k the world!!!!
/dev/world has reached maximal mount count, check forced.