5 ms·
Why do you think Chrome is eating Firefox's lunch? Humorous given that both webkit and from that Chromium are largely comment free. What nonsense are you argui
by huggyface 14y ago
Why do you think Chrome is eating Firefox's lunch?
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.
- flatline3 14y ago> Humorous given that both webkit and from that Chromium are largely comment free. What nonsense are you arguing again? Seriously? http://src.chromium.org/viewvc/chrome/trunk/src/ipc/ipc_channel_proxy.cc?revision=150891&view=markup 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. http://src.chromium.org/viewvc/chrome/trunk/src/ipc/ipc_channel_nacl.cc?revision=146006&view=markup http://src.chromium.org/viewvc/chrome/trunk/src/ipc/ipc_chan... 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.
- huggyface 14y agoAn enormously complex rendering and JavaScript engine. Some laughably irrelevant, trivial comments. Quite a solid proof you have there.
- flatline3 14y agoThose comments are trivial and irrelevant? 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.
- huggyface 14y agoIntellectually lazy? That's a mighty big term for someone like you. 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.
- flatline3 14y agoFailing to document code is to the detriment of future maintainers. Anyone that claims their code is clear and ambiguous without comments is lying to everyone, including themselves, as a means to justify their intellectual laziness. "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.
- jholman 14y agoHey flatline3, I feel your pain, but it's time to stop feeding the troll.
- huggyface 14y agoYou "feel their pain" by tracing through this entire sub-discussion, desperately clicking down-arrow along the way, and then adding some masturbatory, zero-content noise comment to try to cluck with the herd? This is, without doubt, the Worst of Hacker News. My original post mentioned the truism that commenting was a crutch (which to a non-idiot doesn't mean that all commenting is bad, but that when someone is bad at writing or reading code they need to lean on comments in a negative fashion: No longer do they need to write clear, provable code, but instead can inject lots of comments that may or may not correlate with the reality reflected in the code (more often it does not). No longer do they need to understand what code does but instead can just hope and pray that it does something similar to the vague description at the outset). Cue the chorus of hilarious quacks making their utterly stupid, Reddit-quality posts to try to sing with the chorus. Give me a break. Declaring someone a troll is the banal hubris of the intellectually broken.