Did you notice that yourself and I, we both like to be anonymous. It is because the reaction to this kind of topic in any Perl community is nearing some sort of flamewar or in any case something of big proportions.

This is not supposed to happen normally, because you just come with an honest question but people keep on giving dishonest answers, or politically correct answers such as depends on your definition of "production-ready" or lame stuff like for most definitions of "production-ready".

That's really dishonest and it annoys me a lot and I'm sure it annoys you too.

I do appreciate the fact that you are honest Anonymous Monk :)

I do take offence of being accused as having given a dishonest answer.

In another day and age and if you were not hiding behind your anonymous mask, we would have met at dawn on a field at the edge of the town and we would have settled this slight to my honour in a way as befits gentlemen.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

Well, it annoys me when one insists that another must make a judgement call for one. It's worse than dishonest. It's abdication.

Perl 6 is obviously not ready for what 99% of shops would call production. On the other hand, it's an extremely interesting language that can do a lot already and if I were doing a start-up with at least one really smart hacker, I might just base the code on it at this point to get ahead of the curve. Otherwise, it might be nice to use for internal, non-critical tools just to get the exposure, chops, and start giving feedback, test, and bug reports so it can be ready for prime time sooner.

the start-up idea sounds reasonable, but how would Perl6 put you ahead of the curve ?

start giving feedback, test, and bug reports so it can be ready for prime time sooner

this is interesting. but because there only so many(few) active Perl6 people how will your bug reports and tests help ? maybe they have other priorities than what you think is prioritary and they will focus on those while implementing or fixing bugs ?

I agree with this reply, I took time and emailed the group who supports perl6 and received a political answer. I am firm believer that when programmers are forced to responded politically about when something will be completed. The project most likely will never be done who simply doesn't have good direction. This has been well over ten years in the making and every other month someone on the team has a personal issue or the dog is sick pushing back the project. It doesnt take 30 days to state something will or will not be delayed.