in reply to Perl 5 <-> Perl 6 compatibility: a benefit or a mess?

It is definitely a mess. Even with Python, a language that's much more modern, between its current stream and the future P3K stream, there is a need to break the backward compatibility. To entertain P5 in P6, the penalty will become clear very quicklya, and it certainly makes P6 much less attractive in lots of people's eyes.

On the other hand, to look at this from a higher level, the opportunity of success is not very good for Perl 6. With Python and Ruby around, less people will appreciate P6, which is similar and less sophisticated. P6 is taking too long to deliver, and the world does not stop and wait, the moment P6 comes out, it is probably obsolete already in many ways.

  • Comment on Re: Perl 5 <-> Perl 6 compatibility: a benefit or a mess?

Replies are listed 'Best First'.
Re^2: Perl 5 <-> Perl 6 compatibility: a benefit or a mess?
by chromatic (Archbishop) on Jun 18, 2007 at 21:56 UTC
    With Python and Ruby around, less people will appreciate P6, which is similar and less sophisticated.

    I'm exceedingly curious as to how Ruby and Python are more sophisticated than Perl 6. For one example, Perl 6 right now (in both the Pugs and Perl 6 on Parrot implementations) has working Unicode support, which puts it well beyond what Ruby can claim. I don't believe the Perl 6 on Parrot implementation quite has lambdas working (but it's close)... but even Perl 5 supports those better than Python does.

    I could go on, but neither is an exotic feature by any means. (If I were sneaky, I'd ask "Can Python or Ruby catch automagically declared variables yet?")