So, people are using perl6 code at this time? And, if so what are the results? I am wondering are the people who upgrade perl 5 working on perl 6 as well? It just seems it is taking an extremely long time 10 plus years to come out with a production usable version. Second, it seems there has been every excuse in the world on the site as to reasons why this version or a delay occurs every month. Maybe some other open source people should assist with finishing up a production version of perl6?
Re^4: The current state of Perl 6
Replies are listed 'Best First'.
am wondering are the people who upgrade perl 5 working on perl 6 as well?
Most developers either work on Perl 5 or Perl 6 - both take up tremendous amounts of time, and since the code bases don't overlap all that much, there's no good reason for developers to work on both.
It just seems it is taking an extremely long time 10 plus years to come out with a production usable version.
It is. Because Perl 6 has extremely high demands on compiler writers.
Second, it seems there has been every excuse in the world on the site as to reasons why this version or a delay occurs every month.
I've mostly seen reasons, not excuses.
Let me make this perfectly clear: There's no reason why any Perl 6 developer should excuse himself or herself for not having finished something you'd like to see - we're all volunteers. And nobody wants to see Perl 6 "done" more than those people actually working on it.
Maybe some other open source people should assist with finishing up a production version of perl6?
I'd really love to see that. But attracting contributors isn't as easy as saying "maybe somebody else should assist".
If you have any idea how that might be accomplished, I'm eager to hear.
Perl 6 - links to (nearly) everything that is Perl 6.
In such a generally unpleasant and contentious thread, it sure was nice to read your patient and informative reply to some of the main questions. Along with a few other serious replies, I feel that I've gotten a little better sense of what's going on ... without the effort of following the actual work. Thanks.
I cannot agree more with what you wrote, I think this is entirely true. More than a decade has passed since they started writing Perl6.
The problem is they also had a lot of implementation, instead of doing some centralized common effort, they spread like fishes when approaching obstacles in a stream.
Here's some quick statistics on the number of commits
16|James E Keenan (Jim)
35|Jonathan Scott Duff
38|Mark Glines a.k.a. Infinoid
45|Will "Coke" Coleda
229|Moritz A Lenz
232|Jerry Gay a.k.a. particle
796|Patrick R. Michaud
It's pretty clear who the main people are here.
Maybe it's also a problem of competency. Maybe they don't master all the elements needed to write a language. I don't know. But I'm 100% there are reasons for Perl6 not being production-ready yet.
What is interesting to note is that these people are carrying out unpaid work. That means they have fragmented time slices which are used to implement Perl6. Again that's something very important. Also, because it's unpaid work, maybe it's not taken very seriously and the mentality of the whole project is something like yeah, we got this experiment going, and it's going to continue to be an experiment for a looong long time