http://qs321.pair.com?node_id=861721


in reply to Re^8: Will Perl 6 Replace Perl 5?
in thread Will Perl 6 Replace Perl 5?

Yes, but how stable is the specification? How far along Rakudo is isn't that important (at least to me) as the language itself is. It's the language that provides the real long-term stability, not the implementation. For outsiders, it's not obvious how far along the specification is. I assume many parts are fleshed out and really well thought through, while others haven't been touched yet because the implementations aren't there yet and people still need to play around with it. But I can't know what sections are where. So even if I evaluate Rakudo for my use-case today, it doesn't say anything about what will be tomorrow. And it's the tomorrow people are interested in.

And I'm not quibbling over any of those terms. Also, again, I'm not interested in the version numbers.

By the way, you're coming across as quite aggressive. I don't know if that's intentional or not. But just to be clear: I don't (yet) care about Perl 6. At least not from a usage point-of-view. I'd be happy if I had more time for version 5 in fact. So I'm not trying to pressure you into an answer. I just feel that the discussion about version numbers has taken over the discussions about the actual questions that people have.


Ordinary morality is for ordinary people. -- Aleister Crowley

Replies are listed 'Best First'.
Re^10: Will Perl 6 Replace Perl 5?
by chromatic (Archbishop) on Sep 24, 2010 at 03:50 UTC
    Yes, but how stable is the specification?

    I suspect—and speak only for myself here—that the Perl 6.0.0 specification will be complete right about the same time that Rakudo (or another implementation) implements all of the specification.

      That's an awesome answer! I know that you can only speak for yourself, but if the Perl 6 community deems Rakudo a good testbed for the specification, that's something an ecosystem can be built on. If an early-adopter rule-of-thumb is that "stuff that has been in Rakudo for a while is relatively safe," people can use that subset to start writing libraries they feel safe to release.

      Thanks again, since I can now start imagining how a Perl 6 CPAN would form, and know what to watch out for to step on to the Perl 6 train.


      Ordinary morality is for ordinary people. -- Aleister Crowley
        I know that you can only speak for yourself, but if the Perl 6 community deems Rakudo a good testbed for the specification, that's something an ecosystem can be built on.

        Every implementation is a testbed for the specification, and different implementations focus on different aspects.

        Rakudo is just the one that focuses on wide spread usability.

        We are also working on a module ecosystem. There's http://modules.perl6.org/ with a list of modules we know about; there's a prototype module installer being worked on, a prototype smoke tester (results here) and so on.

        It's just that most of the people that are motivated to work on it are involved in far too many other Perl 6 projects, and so often only allocate small time slices for the module ecosystem.

        If somebody wants to shape the Perl 6 ecosystem, now would be great time. We have some modules, and people are asking how to install them. Stepping up now and writing runnable code for a module installer or a module repository would surely be a greatly appreciated by the Perl 6 community.

        Perl 6 - links to (nearly) everything that is Perl 6.