Re^3: The current state of Perl 6
by moritz (Cardinal) on Apr 19, 2010 at 11:23 UTC
|
oppinion on Perl6's production-readiness
Note that this is not what's been discussed in the reddit thread (but rather if it's practical).
Anyway, it's not yet production ready, for most values of "production" that you can come up with.
I do occasionally solve problems in Perl 6 where it's much better suited than Perl 5, but usually when I want something stable that will still work in 2 years without any maintenance, I use Perl 5.
Rakudo is now in need of early adopters to shake out bugs, and to tell the developers which areas need the most work to become "production ready" (which can mean a whole lot of different things depending on othe use case).
Perl 6 - links to (nearly) everything that is Perl 6.
| [reply] |
|
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?
| [reply] |
|
So, people are using perl6 code at this time?
Yes.
And, if so what are the results?
Some people like it, others don't.
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.
| [reply] |
|
|
|
|
|
|
|
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
8|Allison Randal
8|Julian Albo
10|Audrey Tang
13|mberends
15|Leopold Toetsch
16|James E Keenan (Jim)
17|Paul Cochrane
22|Andy Lester
35|Jonathan Scott Duff
35|Kyle Hasselbacher
38|Martin Berends
38|Mark Glines a.k.a. Infinoid
40|Cory Spencer
44|David Romano
45|Will "Coke" Coleda
52|Bernhard Schmalhofer
65|chromatic
97|Stephen Weeks
118|Carl Masak
229|Moritz A Lenz
232|Jerry Gay a.k.a. particle
429|Solomon Foster
477|jnthn
536|Moritz Lenz
796|Patrick R. Michaud
818|pmichaud
1040|Jonathan Worthington
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
| [reply] |
|
|
|
|
|
Re^3: The current state of Perl6
by CountZero (Bishop) on Apr 19, 2010 at 10:36 UTC
|
Depends on your definition of "production ready", but I would not yet use it in any mission critical applications. And with Perl 5.12 now out, I do not yet see a pressing reason to switch to Perl 6 yet.
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
| [reply] |
|
so it's not production-ready.
| [reply] |
|
No, as of now its not. And I think that will be the case for some time to come(May be an year).
Only some one working on the project can give a exact date though.
| [reply] |
|
|
|
|
|
A reply falls below the community's threshold of quality. You may see it by logging in.
|