SoylentNews is people
SoylentNews
After 15 years of development, perl 6 will be officially launched as production ready software in 2015.
https://fosdem.org/2015/schedule/event/get_ready_to_party/
Who knows, 2015 may also be the year of the linux desktop, unless HURD is also ready for prime time.
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
To stand and be still,
At the Birkenhead drill,
Is a damned tough bullet to chew.
-- Rudyard Kipling
(Score: 2) by PizzaRollPlinkett on Saturday November 08 2014, @11:36AM
I've thought for a decade or more that Perl 6 was the best thing that ever happened to Perl. While all the designers and change-for-the-sake-of-change people worked on Perl 6 as the be-all and end-all of language design, and it became a black hole, everyone else used Perl 5 to get productive work done. Perl 5 was immune from huge changes (especially the kind that would break existing code), and stayed stable. This allowed CPAN to be one of the greatest code-reuse repositories ever, because once someone wrote something, it kept working.
Perl 5 has outlasted every fad and has been dumped on for decades, but people just ignore all that and keep doing productive work with it! I imagine Perl 5 will outlast Perl 6, too.
Full disclosure: I've used Perl since mumble mumble - wow, I'm getting old. I'm in my third decade with the language.
(E-mail me if you want a pizza roll!)
(Score: 1, Interesting) by Anonymous Coward on Saturday November 08 2014, @02:34PM
You've tried to make Perl 5's stagnation sound like a good thing. It isn't a good thing at all. Python, and even Ruby, have eaten Perl's lunch.
(Score: 0) by Anonymous Coward on Saturday November 08 2014, @07:33PM
yeah, and node.js tosses [urbandictionary.com] perl's salad!
(Score: 2) by bzipitidoo on Saturday November 08 2014, @07:31PM
CPAN is hardly immune to breakage. Several times I've had to roll back to old versions of CPAN modules to keep Perl programs functioning. The individuals who maintain modules on CPAN don't test their changes that carefully or thoroughly.
I've been looking forward to Perl 6. One of the coolest things about it may make much of CPAN unnecessary. Lot of CPAN modules are wrapper code for C libraries. Perl 6 is supposed to be a lot better at hooking directly into libraries.
(Score: 2) by frojack on Sunday November 09 2014, @02:25AM
But CPAN will probably still be around, because, quite frankly, it was the one good thing Perl had going for it.
Put in a module to CPAN and its available everywhere. You could lock it down to specific versions of modules so some careless developer didn't break all of your stuff. You could also esily make your own local version so that something under active development didn't bite you. And of course you never had to run CPAN at all if you didn't want to.
But I never had any significant problem. It happened so infrequently, (three times that I recall) that it was never a big deal. Besides it was occasionally entertaining to see all the bitch-mail that could get generated.
I remember the early days of Spamassassin when it was totally written in Perl.
No, you are mistaken. I've always had this sig.
(Score: 0) by Anonymous Coward on Monday November 10 2014, @05:24PM
This should be modded 7 for sublime. You sir are a genius.