Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Ok, so xkcd is a little on the popular side, but...

    I feel that it touches on one of perls greatest weaknesses - never knowing if a subroutene is unused, and subsequently the fear of deletion - the danger of inevitable kruft has always been in my eyes perls' achilles heel.

    I love the language to bits - though I admit I don't use it enough, the failure of other programming mediums to understand return if argument rubish continues to disapoint.

    Its just that having a language that seems to err on the dynamic as possible side of the fence, I feel facilitates the argument that it could give the novice too much power, and if I ran a business could give me a source of worry - programmers wages are expensive enough without worrying about the accidental damage they can do to your business.

    Is it really wrong to ensure that a programmer requesting to perform the dark arts knows which end of the broom to grab?

    Disclaimer: just back from pub.