I've been installing new releases quite often. I'm perl5 has become quite xml-ized over the
past 5 years, which has repeatedly required me to upgrade (more so out of simplicity and
sometimes when the cpan shell or depends break)
I'm beginning to get this.
Perl5 is a language that will continue to subsist long after Perl6 comes along.
Perl6 is a new language. It is not perl5, or a replacement for perl5.
Again, so Perl 6 is a new language.
I'm having a hard time detaching myself from wanting a perl5 successor. I guess the regex
changes are part way to pushing me over the wall. But then, the changes outlined in
Perl6::Perl5::Differences bring me back to my much loved Perl-reality.
Perl6 isn't that much different. The language changes (the things we truely care about as
developers) are subtle, and imo, desirable.
We want Perl6 to be Perl5's successor. But it's not. It could be. But it's not. It looks like
it should. But it's not.
We'll see whether the wait was worth it if other languages utilise Parrot successfully. I
liked the original idea behind Parrot - a unified JIT system (? forgive me - i see Parrot as
the java-for-all VM well all wanted) - but unfortunately we have fragmentation with Pugs
(implemented in Haskell... serious WTF territory there) miniperl etc...
With perl.tar.gz, ActiveState Perl and now Strawberry Perl, we've always been assured we'd get
Larry's Perl. The same Perl code... the same tree. Now it's all a little confusing.
Multiple implementations of the same language passing the a shared test suite isnt what I
expected its hard enough coding for one; just look at the C# compiler bugs and runtime
cockups! Is Perl6 in-your-face-anti-Java? The many implementation language with cant-run-here
quirks Gosling has tried so hard to avoid!?
The Perl identity crisis continues....