We could bitch that we don't do "C for loops"

Never, that would be bitchy and lame

...but where does it end?

If you never start with such noise, you don't have to worry about the end :) Elaborate on style only when the OP ask for it (or its absolutely critical), present it as better options (because that is what they are, choices) but don't be a bully about it, otherwise don't scare away the newbies.

See also How to help? and

• RFC - shortform posting guidance for newcomers
• Put some of the posting guidelines directly above the posting form:
• Give a fish or teach to fish?
• Talk 9: On Fish
• RFC: Review of "Seekers of Perl Wisdom" description?
• Don't go all PerlMonks on me
• Perl best practices fanatism
• Module::Starter (or ::PBP) and Module::Build -- how do I configure the License and Copyright?
• Why Create Coding Standards and Perform Code Reviews?
• Why it is important to counter FUD.
• Thread on Joel on software forum : "I hate Perl programmers."
• PBP: Code Layout
• Best practice or cargo cult?
• Should I leave behind beautiful code or readable code?
• Modern Perl and the Future of Perl
• Module Bloat and the Best Solution