Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • I freely confess that I'm one of the folks tired of waiting for Perl 6, but not because I think it's being handled particularly poorly or that folks aren't working hard enough. It's just that after years of waiting, I want to something I can use in a production environment. Yes, mistakes have been made here and there (and there and there), but the people involved are human and people should be more willing to forgive.

    Having seen just a little bit of what's going on with Parrot and Perl 6, I'm actually q

  • You don't think that the feeling of "no one wants to talk about problem X" and "There aren't enough people to do the work." are related?

    Or how about the barriers to entry to help out? Real or perceived I've noticed a definite feeling of "I would never deign to tell $perl_deity that $x is wrong. $perl_deity is so much smarter than me"

    • "I would never deign to tell $perl_deity that $x is wrong. $perl_deity is so much smarter than me"

      That doesn't sound like a barrier to entry for helping out, that sounds like confusion about what the words "wrong" and "smarter" mean. If someone sees some '$x' they think is a problem, then either they're haven't researched it enough, or they are wrong and the documentation isn't clear enough about why, or they're right and the problem needs attention. As far as real barriers, there is no social barrier t

      • "Audrey hands out commit bits like a drug dealer drumming up more business." LOL!

        If only there were more pushers, and maybe some money changing hands.

        I must confess that I have not been involved in Perl6 as much as I would like. I have enough demons as it is and not enough daemons.

    • If by some chance you consider me a Perl deity (guru maybe, if you squint at Nat's Seven Stages chart and ignore a few steps), then please feel free to tell me I'm wrong. I write about Perl more than most programmers, so the volume of my opinions makes it likely that I'll be wrong often.

      • Indeed, you shouldn't hold back.

        I tell him he's wrong all the time, and the result has (mostly) been better code. :)
    • I would never deign to tell $perl_deity that $x is wrong. $perl_deity is so much smarter than me.

      As someone whose specific job it is to tell Larry when I think he's wrong, I can certainly empathize with that trepidation. ;-)

      But I can also tell you that bona fide @perl_deities are smart enough to know that they're not always smart enough. And humble enough to welcome corrections when they're needed.

      The thing I've found most useful (both in telling someone else they're wrong, and in being told mysel

      • Here is a rule I live by that the Marines taught me. Never bitch unless you have at least two suggestions for improvement.

        • Oh neat, I specifically like the "at least 2" part.

          (adds it to his "unless you have a better way, and are willing to do the work if you have to")
  • 1st let me say I DO have a right to spout because I, for one, actually did write a large portion of Parrot from 01 to 04.

    >There aren't enough people to do the work.

    Chromatic, you are only half right, or maybe you are right now, but retroactively wrong. There WERE enough people to do the work. Dan left after I left for the same reason that I left. People issues. Leo is very likely a great guy, in person, but he was hard to work with, and he was just plain rude over email. So now he is the patch monster wi