the only thing you can learn from that is that you have to port all the(important) Perl5 modules --> Perl6 early so when it's out people won't be able to complain about this.
but since Perl6 is still in development devs will face serious bugs that they won't really be able to fix themselves because they don't know the internals of the compiler in order to fix those bugs.
Re^2: The current state of Perl6
Replies are listed 'Best First'.
Why do think Perl 6 should ship with a vars module? Or with Encode, when buffers have .decode and strings .encode methods?
IMHO there are also a whole lot of modules in the Perl 5 core that have no good reason for being there (like Text::Soundex)
I also suspect that there will be quite a difference between "core" Perl 6 and Perl 6 distributions. I see no reason why "core" should contain something like CGI, but most distributions will probably ship something like that anyway.
Well the point is that for any thing that could you could do with the Perl 5 standard library should either be available with Perl 6 language or the standard library. If some thing was there in Perl 5(Even as a module) and not in Perl 6 why should some one bother to shift to Perl 6?