Re^2: Why Perl 6 is taking so !@#$ long

You summarized very well, so well that I better understand my own feelings about the subject: I browsed summaries on said lists, and your summary of summaries now makes things better structured.

One point I want to share my opinion though:

... note that I've criticized Parrot, not Perl 6. That's because I believe that Perl 6 will happen. It won't hit all of its original goals, but thanks to Audrey there is an implementation coming along.

Actually Autrijus stepped in very unexpected and interesting manner:

He made an unbeleivable implementation of perl 6, and this made great boost of development. Many people became beleivers of perl6 and stepped into development. Every person can receive committer bit.
Many people looked seriously on Haskell.
Now there are much less stupid claimings about Python being useless only because it is whitespace-dependant (Haskell is whitespace-dependant but very serious language)
Pugs, while quite brilliant implementation, supports and depends on parrot. I think this is more of political decision other than technical. This way more parrot people became involved in Pugs and no disappointed in parrot people.

Before Pugs and after pugs are very different volume of efforts spent on Perl6, so actually Pugs awakened perl6 and parrot, because now people see direction.

sorry for English

Best regards,
Courage, the Cowardly Dog

Comment on Re^2: Why Perl 6 is taking so !@#$ long

Replies are listed 'Best First'.
Re^3: Why Perl 6 is taking so !@#$ long by duff (Parson) on Mar 02, 2006 at 15:58 UTC
Pugs, while quite brilliant implementation, supports and depends on parrot I don't think that pugs depends on parrot in any way. Sure, if you want to use PGE (which is written in PIR), then you need a working parrot somewhere. But that's just a small part of what you get from pugs. Besides, now that there's a prototype implementation of PGE, who's to say that someone won't recreate it using Parsec? (In fact, I believe Audrey has already started doing this) Just because some small part of pugs uses parrot doesn't mean that that part can't be swapped out with a non-parrot version at any time. The real question is: Will we get a workable perl6 compiler out of all this? :-) duff	[reply]

Replies are listed 'Best First'.

Re^3: Why Perl 6 is taking so !@#$ long
by duff (Parson) on Mar 02, 2006 at 15:58 UTC

Pugs, while quite brilliant implementation, supports and depends on parrot

I don't think that pugs depends on parrot in any way. Sure, if you want to use PGE (which is written in PIR), then you need a working parrot somewhere. But that's just a small part of what you get from pugs.

Besides, now that there's a prototype implementation of PGE, who's to say that someone won't recreate it using Parsec? (In fact, I believe Audrey has already started doing this) Just because some small part of pugs uses parrot doesn't mean that that part can't be swapped out with a non-parrot version at any time.

The real question is: Will we get a workable perl6 compiler out of all this? :-)

duff

[reply]