|Syntactic Confectionery Delight|
I speak only for myself here as someone who gets paid to write Perl code.
Just give me a Perl6 implementation i can depend on. I need to start writing scripts and modules and ditribute them on CPAN. And i need some reasonable guarantees that i don't have to do major rewrites every few months just to keep my code working.
Rakudo doesn't have to be "feature complete" or be "highly optimized". To attract developers (who may write Perl code for a living), it needs to be stable enough that it's worth the (company) time to start writing code for it that it more complex than "Hello World" and more useful than self-test scripts.
Stop breaking things because you "need to optimize". Frankly, unless Perl6 gets at least one stable, extensible Interpreter (e.g. not major rewrites every time you feel like it), there won't be a big community writing actual, useful code for it that starts to attract even more developers. Ergo it wont run any code that needs an optimized interpreter...
Really, give me something i can show to my boss as a reasonable good choice to implement software with that will run for years, maybe a decade.
"I know what i'm doing! Look, what could possibly go wrong? All i have to pull this lever like so, and then press this button here like ArghhhhhaaAaAAAaaagraaaAAaa!!!"
In reply to Re^9: Perl 6: Managing breakages across Rakudo versions