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.
  • Weren't you the guy just taking a big dump on the Chicago.pm list? Why not list all the things that you dump on (including use.perl, which you suggested should be taken over by force)? So, when are you going to stop taking big dumps?

    So what if people dump on ideas? It's better than telling people that public debate is forbidden. Perhaps you just don't like open discussion and freedom.

    • However "dumping" and exchanging ideas on something are totally different things.

      "I am not sure why you did this could you fill me in?" is much better than "You did what? That sucks and you are stupid for doing it!". Even if after you get the explanation and don't agree you can still say "I see what you did but I don't think it will work."

      So the Perl community should foster an exchange of ideas and polite discourse and discourage "dumping".

      I don't know any of the "background" issues that caused the article to be written but I think the premise is a good one.
      • I agree with you. same goes to lines like:

        "why do you write this module when there are dozen of them on CPAN do the same thing. stop wasting your time."

        that's the sorta thing discourages people to innovate and invent something better.