Read almost any non-trivial successful project for good examples. The Linux kernel. Firefox. etc. The frequency and verbosity of comments tends to have a direct correlation with the simplicity of the code (which is the exact opposite of normal expectations).
Have you written any large projects that you've had to maintain over years, or worked with large teams, or handed off maintenance of a large project to others?
To your questions, while you're rhetorically asking, trying to wink to the crowd in the implication that the answers are telling, yes, actually I have. To very good effect. I'm speaking from actual experience here, not just the hilarious patter of the bottomfeeder that is far too typical on HN.
No.
> "Messes". Indeed.
Yes, messes. Why do you think Chrome is eating Firefox's lunch ? Google has both a better-implemented product and sufficient marketing clout to push it.
Have you worked on Linux kernel code?
> I'm speaking from actual experience here, not just the hilarious patter of the bottomfeeder that is far too typical on HN.
What have you worked on?
I've worked on FreeBSD, Mac OS X, and an assortment of smaller widely used software projects, including user-facing applications.
Humorous given that both webkit and from that Chromium are largely comment free. What nonsense are you arguing again?
I've worked on FreeBSD, Mac OS X, and an assortment of smaller widely used software projects, including user-facing applications.
"Worked on" in HN parlance means "I did a coop term and wrote some test cases for some irrelevant little utility". Given your comical claims about Linux and Firefox re: Chrome, I have enough information about your skills.
Seriously?
http://src.chromium.org/viewvc/chrome/trunk/src/ipc/ipc_chan...
// If the channel has already been created, then we need to send this
// message so that the filter gets access to the Channel.
And so on.
> "Worked on" in HN parlance means "I did a coop term and wrote some test cases for some irrelevant little utility".
Please go back to Reddit.
You clearly have no idea what you're talking about. I hope I never get stuck cleaning up your messes, but chances are that someone as intellectually lazy as you -- if not you -- will leave me an uncommented code base to maintain.
The fact that you actively advocate intellectual laziness is distressing.
Further it's utterly astonishing that you would equate writing clear and non-ambiguous code rather than nebulous code of uncertain purpose -- like the example Chromium code you linked -- is "intellectual laziness". That you hold good coding as deficient compared to lazy commenting is hardly surprising given your comments.
"I don't need to comment" is really "I don't want to document my work because that's boring and I'm much too smart to need to do that".
You're not that smart. If you were, you'd realize just how dumb everyone is, and thus, just how necessary comments are.