in reply to Re^8: The current state of Perl6
in thread The current state of Perl6
I question your belief that concurrency implies the success of a language. Let's consider the case of Erlang. It has the strongest implementation of concurrency. I do not think it has been very succesful. I do not see Erlang adopted everywhere just because it can do concurrency well. In fact, C and C++ are still widely used for it.
There is a well-known myth in the Perl community that threads are the worst possible thing, however that is because Perl programmers which deal mostly with web programming don't study threads well enough so of course they cannot use them. As a retreat, they use POE instead which is not real concurrency.
They hide behind excuses of the form "threads are too complicated for the human brain". That is of course complete nonsense because threads are well studied and can be learned, but what can you ask of web developers who deal with CSS , Javascript, HTML. They concentrate on completely different things.
But let's return to Perl 6, Parrot does not support concurrency. Let us suppose that concurrency will be implemented. Who would use it ? Since most Perl programmers already have the prejudice that threads are evil and bad.
Let's also consider another aspect. As it stands today Perl is mostly used by sysadmins(although I do not like to say this), what use would sysadmins have for concurrency. Most sysadmins are not well-trained programmers.
I think you should not assume oppinions of people who evangelize a language or the other. Instead you should judge them with your own mind and see for yourself if they have been adopted or not.