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.
  • Hidden agenda? Hogwash.

    My impression is that chromatic has been quite clear and forthright with his intentions. He has looked at how the Perl 5 project has been managed, done some root cause analysis, and proposed some improvements to the process based on what his own experiences have found working well.

    Nothing wrong with that. I fact, we should thank chromatic for bothering to look at something that very few open source projects consider at all.

    • He provided crappy and stupid advice, and when told to shut up, politely at the time, he opened a blog to yell louder.

      No thanks for being stubborn, sorry.

      • No thanks for being stubborn, sorry.

        Why not?

        What if he's right?

        --

        --
        xoa

        • Well, if he's right, then all of the people who have experience in maintaining perl 5 are wrong. Which seems very, very, unlikely, no?

          • if he's right, then all of the people who have experience in maintaining perl 5 are wrong. Which seems very, very, unlikely, no?

            No, I don't think that logic follows whatsoever. It's entirely possible that the way that Perl 5 has been doing things for years is not as good as the way(s) that chromatic is suggesting. What's more, what I've read of chromatic's arguments make sense.

            --

            --
            xoa

          • Well, if he's right, then all of the people who have experience in maintaining perl 5 are wrong. Which seems very, very, unlikely, no?

            What's with the absolutism? Cannot they both be partially right and partially wrong?