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.
  • I bet I could even help him check out Parrot on his laptop such that he could type cd languages/perl6/ and make test and see for himself how things are.

    It's not about me, it's about everyone else. I'm not the one asking where it's at, because I know the "it'll be done when it's done answer." It's for everyone else. It's for the guys at the Linux user group meeting I went to last night who when they heard I used Perl immediately asked "When is Perl 6 coming out?"

    Why is it so awful that people want to know what's going on, without having to check out a source tree and read through arcane documents?

    --

    --
    xoa

    • It's not that people ask the questions, it's that they don't bother to find out. It's not a question they really care about enough to google.

      And, apparently, it's a question you don't have a good answer to. You don't need to know about deadlines and project charts to distill into a couple of sentences what the Perl 6 team says over and over again. People seemed satisfied with the answers I give to the same question. Why you can't do the same is boggling.

      I think you're just interested in stirring the shit, t
      • It's not a question they really care about enough to google.

        There is no answer to "When is Perl 6 coming out" that is more than "It'll be done when it's done," Googleable or not.

        I don't want a date. I want something more than "It'll be done when it's done." Somewhere between declaring a day on the calendar, and saying "Uh, hell, I dunno", there's a middle ground. That's what I want.

        Why you can't do the same is boggling.

        Because nobody I've ever given the answer of "It'll be done when it's done"

        --

        --
        xoa

        • If "It will be done when it's done" isn't a satisfying answer, stop giving it. You think you're a smart guy, so look at the information and come up with the real answer. I've just posted my talking points. I don't have the same trouble you do, apparently. If you want to claim to be the PR guy, you need to be the person to take all the information and distill it for the public, not the guy spreading the disinformation and inflaming uninformed opinions. It's not that people ask the question, it's your inabili
        • Because nobody I've ever given the answer of "It'll be done when it's done" is satisfied with it.

          Perhaps you should explain why that's the answer, as I usually do. That turns the answer from "We're not going to tell you" or "We don't want to tell you" to "We can't really answer that question, but here's what we know so far."

    • Patrick has made a number of excellent progress reports recently - http://use.perl.org/~pmichaud/journal [perl.org]

      chromatic has been posting meeting minutes from the p6 developers for ages - http://use.perl.org/~chromatic/journal [perl.org]

      There's a Pugs Wiki [pugscode.org] with links to lots of useful stuff like the documentation [perlcabal.org],
      the Pugs Blog [blogs.com], logs of the Pugs IRC channel [perlgeek.de], a "run perl 6 in your browser [pugscode.org] interface, and the TPF Perl 6 Wiki [perlfoundation.org].

      I found those by using only one resource as a starting point: Google for "perl 6" and clicking around.

      It
      --
      rjbs
      • It would be nice if perl.org's information on Perl 6 was not so outdated. Maybe its perl6 pages could just link to the wiki. It would be nice if the p6l summaries started again, but I sure as hell don't have the time, and I don't know who does.

        I'm sure I could find a way to update them once in a while, but I certainly don't have the time to maintain them as a long-term project (and I think I ought to be writing code or documentation instead). This is one of our biggest problems; we don't know where peo

        • Yeah, I am not arguing that anyone should be taken off doing what they're doing. I'm just saying what would be nice.

          Pie would be nice, too. Chocolate silk with a graham cracker crust. Mmm!

          Is the Perl 6 wiki the most kept-up-to-date place? I wouldn't mind spending a little time finding and trying to deal with a few of the top Google results to get them to point to the right place, either with a link or a redirection. Like, a few hours at least. Let me know and I'll give it a quick go.
          --
          rjbs
          • Is the Perl 6 wiki the most kept-up-to-date place?

            Let's use it that way for now. If you (or anyone reading this) updates the wiki, I'll get parrotcode.org and dev.perl.org/perl6 updated to point to the wiki.

            • I don't update the wiki. I only keep a corner of my eye pointed at Parrot and Perl 6. I meant: if the TPF P6 wiki is the best resource (and it seems to be) then I will work on getting other resources to point to it. I'll drop perl.org a line about dev.perl.org, and will update other wikis around.
              --
              rjbs
        • People are always going to be misinformed. It doesn't matter what the topic is. It's not the problem anyone should be working to solve. You can lead a horse to water, and all that.

          However, if TPF doesn't want to keep things like dev.perl.org up to date, then the horses don't even have the option of water. I guess that would be a question for someone in TPF's PR department.