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.

Perl 6 Hacking At GPW 8 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • I'm really sorry to hear that, Jonathan!

    While I myself will continue to argue that Perl6 ist vaporware until it is actually released, I will kick people from the Workshop if they attack other people personally.

    I hope the guy will have the balls to publicly apologize to you without any wenn und aber or else I'll try to track him down and refuse to let him attend any further German Perl Workshops.

    --
    Cynic, n.: A blackguard whose faulty vision sees things as they are, not as they ought to be. -- The Devil's Dictionary

    • While I myself will continue to argue that [Perl6] ist vaporware until it is actually released...

      Seriously? New Rakudo [rakudo.org] release next Wednesday, just like every month.

      • You keep saying that [perlmonks.org], but I guess what people mean by "Perl6" is not "Something that somebody decided to slap the label 'Perl6' on", or "Some executable named perl6", but something that lives up to the promises made by Damian and others, and the venture into Science Fiction, published by O'Reilly. I guess you will have to put up with telling people that Rakudo is Perl6 even after the release of Duke Nukem Forever.

        I'm still waiting for my flying car.

        • I'm still waiting for my flying car.

          You're no dummy. I know familiar with how community-driven software works. I can't understand where the feeling of entitlement comes from that drives you to complain continually that we haven't somehow magically pooled all of our volunteer time to produce everything what you want on precisely your schedule for exactly the budget you've given us to work with.

          On behalf of every volunteer (such as Allison, Jonathan, Patrick, Larry, Damian, Audrey, and Jerry) who's ac

          • You misunderstand me. I'm not complaining about that Perl6 is not here. The only thing I'm pointing at is your constant railing against such claims as:

            [Perl6] ist vaporware until it is actually released...

            You claim that

            Seriously? New Rakudo release next Wednesday, just like every month.

            as if that were any indication to that Perl6 were actually "done" in any way.

            The progress that has been made in the last few years is amazing, but Perl6 is in no way "done" or "ready". Rakudo has a long way to go to

            • Rakudo does in no way change the vaporware of [Perl 6]...

              The fact that multiple implementations exist and people can use them (hey, I wrote working Perl 6 code two and a half year ago) doesn't mean that the software actually exists outside of a hidden code repository that no one outside of the company can see or even outside the minds of the marketing department?

              If you downloaded and build Rakudo right now, you might see that it supports features natively that Perl 5 doesn't have.

              If you want to rede

              • I wrote working Perl6 code two years and 10 months ago myself [perl.org], thank you. But that does not mean that the then implementation of Perl6 included any features that differentiated Perl6 from Perl5.

                If you get all sorts of righteous indignation knotted up inside when the people actually doing the work to make all of these lovely features exist start saying "Hey, this part works now, and we release a new stable version every month in case you don't want to check out trunk continually," well, that's one sort of hobby I suppose.

                I haven't seen you saying "Hey, this part works now", I've only seen you claiming that "You can have perl6 today", as if a binary named perl6 were what the people doubting Perl6 cared about.

                You might want to quote me very carefully if you think I've ever said that any Perl 6 implementation is currently complete, however.

                ... which actually is the benchmark by which I go - before the Perl6 team hasn't said "This is worthy of a 1.0 release" and has released a "press release" claiming that "We are satisfied with it", all your "You can use it already (except, it's not done yet and we might shuffle around the operators three times while you download)" just means that, "it's not done yet". Which is why I find it misleading when you equate Perl6 releases with Rakudo releases. You can have as many Rakudo releases as there are months in the year, but that doesn't mean anything in the progress of Perl6.

                Feel free to replace "It's not done yet" with the more positive "We're working on it", if that makes you feel better. It also might create a more positive level of communication between you and the people doubting Perl6 if instead of pointing them to Rakudo as if it were Perl6, you pointed them to Rakudo and told them what features it already has, or even better, that the features they were missing in Perl5 it are already implemented in Rakudo.

                Representing Rakudo as the answer to "When Perl6 is released" is, again, misleading. Representing Rakudo as "This is where we're currently at" might not give you the vindicative feel of "PREL SIX IZ HERE OMGZ", but it might also be a more direct contribution to the discussion of where Perl6, as currently implemented, stands on the vaporware scale.

                • You can have as many Rakudo releases as there are months in the year, but that doesn't mean anything in the progress of [Perl 6].

                  I only responded to quote that sentence. You, sir, left me speechless. Few people do.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.