in reply to Re: If Parrot comes, can Rakudo be far behind?
in thread If Parrot comes, can Rakudo be far behind?

What a pity! Our company will be kicking off a new project on 2010. I had hoped to do my part in perl6.

Besides, I feel I fall in a little bit embarrassed situation. perl6 is much different with perl5. You can find a great many of P5 modules on CPAN, but perl5's grammar of OO taste not good(for other programmers); perl6's grammar is elegant, exuberant, and also TMTOWTDI, but Rakudo is not mature enough. Which one should I corrage my colleagues and friends to learn?



I am trying to improve my English skills, if you see a mistake please feel free to reply or /msg me a correction

  • Comment on Re^2: If Parrot comes, can Rakudo be far behind?

Replies are listed 'Best First'.
Re^3: If Parrot comes, can Rakudo be far behind?
by moritz (Cardinal) on Mar 19, 2009 at 09:50 UTC
    If you want it come out faster, you can always contribute.

    If you don't like Perl 5's OO system, maybe Moose is something for you? It's inspired by Perl 6's OO system.

    Grammars are a killer application indeed, but they still need some more work in Rakudo.

      For me, perl5's OO is never a problem. And I'm happy to find that bless is still in perl6.

      But my question is when, not what. If possible, I certainly want to introduce perl6 to my friends instead of perl5 (think of meta-op, feed, new regex grammar.... Compared to perl5, many ideas deserve Wow!)

      so, Does rakudo team prefer to developing some parts such as IO, concurrcy or regex so that people can write more useful codes in perl6?

      Sorry for my so many questions on perl6. I can't connect to IRC for safe policy of coperation. :(


      I am trying to improve my English skills, if you see a mistake please feel free to reply or /msg me a correction

        so, Does rakudo team prefer to developing some parts such as IO, concurrcy or regex so that people can write more useful codes in perl6?

        The developing goals of the core developers are documented in the roadmap.

        The problem with IO is that the spec is still rather immature, because no implementation has delved too deep into it. Somebody has to do something about that, but it seems we haven't found that somebody yet.