dskoll certainly has valid concerns, but he turns into a real asshole as the thread continues:
I believe the improvements in speed and memory required to make Perl 6 competitive with Perl 5 are unprecedented in the history of computer science.
This is a ridiculous statement, of course things have been optimized by 95% before. Given the specific explanations given by the devs about the wholly unoptimized state of the project along with planned optimizations, it seems well within the realm of possibility.
I'm not sure what the chip on this guys shoulder is, but it sounds like he just wants perl5. He gives no consideration for the innovation and creativity behind perl6. If he doesn't give a shit about all the advanced features then stick with perl5 for god's sake, it's well proven and it's not going anywhere. But to argue ad nauseam about the impossibility of an "adequate" optimization from a totally ignorant position is pretty offensive.
To compare the performance of the mature, optimized Perl 5 core to the freshly baked, feature rich Perl 6 is shortsighted in the extreme.
The Perl 5 runtime is hard to extend, meaning that using the modern additions to the language (notably Moose), comes with a significant start up penalty. This can not be easily overcome.
Perl 6 has a Grammar, Perl 5 only has an implementation (only perl5 can parse Perl5). There is a lot of opportunity for making Perl 6 nice and fast, certainly fast enough for the larger complex applications it is designed to support.
Perl 6 is not trying to compete with Perl 5 on one line throw away scripts. Not yet anyway.
http://www.modernperlbooks.com/mt/2010/07/an-accurate-compar...
Comes across to me like chicken-little syndrome.
I really wish that in the near-ish future some group of people, be it a company, research group or just a bunch of hackers would create something that would cross-breed the best ideas of say Lisp, Haskell and Python in a coherent way to create something really fascinating.
The ParrotVM team did publish a precise roadmap a few years back and I believe the optimization wasn't due to circa version 3 or 4? (ParrotVM is currently at 2.6).
NB. Unfortunately I can't find the original roadmap I'm referring to at moment because it may not have made the Rakudo move from svn to git?
Non Project Member makes a decent point about performance, but does so in an incredibly presumptuous, entitled, non-helpful way.
Project Members make a lot noise and had waves about pre-production, non-optimized versions, etc., but never come out and say "Yes, version n+1 of our project will most likely use more ram and run slower on the same hardware as version N of our project"
Needs some optimizations? Sure.
