Slashdot Mirror


Perl 6 Released (wordpress.com)

Earlier this month, we noted the Perl 6 advent calendar. Now, an anonymous reader writes to note that, right on schedule, and after 15 years of work, Perl 6 has been released. The top two bullet points in the linked description say that the newest Perl "retains the core values of Perl: expressiveness, getting the job done, taking influences from natural language, and pushing the boundaries of language design," and that is "has clean, modern syntax, rooted in familiar constructs but revisiting and revising the things that needed it." However, while it's nice to see Perl 6 reach official release, the team behind it takes pains to note that work goes on: "We will continue to ship monthly releases, which will continue to improve performance and our user’s experience." Further, "[T]his Rakudo release is not considered the primary deliverable for this Christmas; it is the language specification, known as “roast” (Repository Of All Spec Tests), that is considered the primary deliverable."

145 comments

  1. Perl 6 by randalware · · Score: 2

    First post,

    I love Perl

    --
    This is my opinion based on what little I know and understand of the rumors and lies Thanks, Randal
    1. Re:Perl 6 by Anonymous Coward · · Score: 0

      WTF is Perl 6 for? If I can't copy my Perl 5 code to it, it's completely useless!

    2. Re:Perl 6 by Anonymous Coward · · Score: 0

      To accommodate you, there's amodule Inline::Perl5 that you can use in Perl 6 to use virtually anything from Perl 5.
      https://github.com/niner/Inline-Perl5

      Plus, Perl 6 on itself is a beautiful, useful, and modern language that you can use, and be happy with, if you set aside some strong feelings.

  2. That old chestnut? LOL. by mfearby · · Score: 3, Informative

    Yawn. The world has moved on. I used Perl 15 years ago but Perl 6 has taken far too long. Why should I use it now over anything else?

    1. Re:That old chestnut? LOL. by Anonymous Coward · · Score: 3, Interesting

      Are you kidding? I'm still coding in Forth!

    2. Re:That old chestnut? LOL. by randalware · · Score: 3, Interesting

      I do that too...

      Forth is great too....

      small powerfull & highly customizable

      --
      This is my opinion based on what little I know and understand of the rumors and lies Thanks, Randal
    3. Re:That old chestnut? LOL. by ShakaUVM · · Score: 1

      >Yawn. The world has moved on. I used Perl 15 years ago but Perl 6 has taken far too long. Why should I use it now over anything else?

      To be fair, the first C++ standard took forever to come out (in '98), and then they didn't come out with a significant revision again for 13 years, but C++11 was well worth the wait.

    4. Re:That old chestnut? LOL. by Aighearach · · Score: 2

      I got tired of waiting for Perl 6 and switched to Ruby... 11 years ago.

      I think the only reason would be, "I use Perl and I like the new stuff." If that isn't you, this probably isn't your stop.

    5. Re: That old chestnut? LOL. by Anonymous Coward · · Score: 0

      ror is soo last decade. Cool kids use Erlang on rails aka aka Techno Outlaw Psycobitch!

    6. Re: That old chestnut? LOL. by Anonymous Coward · · Score: 0

      What does Ruby have to do with Rails?

    7. Re:That old chestnut? LOL. by shutdown+-p+now · · Score: 4, Informative

      The thing about C++ is that in all that time, no-one has come up with an acceptable replacement, so people stuck to what they had.

      Not so with Perl.

    8. Re: That old chestnut? LOL. by Anonymous Coward · · Score: 0

      Getting Railed Ruined Ruby's Reputation. -PCP

    9. Re:That old chestnut? LOL. by Anonymous Coward · · Score: 0

      Why did you even wait for Perl 6? Perl 5 has worked well for at least the past decade and a half.

    10. Re:That old chestnut? LOL. by Anonymous Coward · · Score: 0

      I got tired of waiting for Perl 6 and switched to Ruby... 11 years ago.

      I think the only reason would be, "I use Perl and I like the new stuff." If that isn't you, this probably isn't your stop.

      Perl is still the go-to language for text processing and systems integration by professionals. Millenials and their hipster ilk cannot grok Perl and complain it is too difficult. Get off my lawn you damn punk!

    11. Re:That old chestnut? LOL. by Anonymous Coward · · Score: 0

      I hate it when the creator of a programming language feels the need to add "features." We did not need object-oriented Perl when it was introduced. If Larry Wall, with all due respect, wanted to implement an object-oriented language for text processing he should have created a new language and not called it Perl. He could have named it Pearl or Oyster.

    12. Re:That old chestnut? LOL. by Anonymous Coward · · Score: 2, Informative

      The thing about C++ is that in all that time, no-one has come up with an acceptable replacement, so people stuck to what they had.

      Not so with Perl.

      The thing about Lisp (which came out in 1958) is that in all that time, no-one has come up with an acceptable replacement. Greenspun's tenth rule of programming: Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp. Well, perhaps Smalltalk.

    13. Re:That old chestnut? LOL. by JustOK · · Score: 1

      How many years ago did you use Perl 15?

      --
      rewriting history since 2109
    14. Re:That old chestnut? LOL. by dbIII · · Score: 1

      Look at PHP as normally used - "anything else" is an improvement.
      It may as well be Perl again.

    15. Re: That old chestnut? LOL. by DrXym · · Score: 1

      C++ has largely been backwards compatible (even when it shouldn't). It means someone can recompile their code with a C++11 compiler and generally it still works. Conversely feed your old Python, Perl or PHP code into the latest version and everything falls over in a heap.

    16. Re:That old chestnut? LOL. by plopez · · Score: 1

      Now that you've (pl.) posted this HR will be requiring it.

      --
      putting the 'B' in LGBTQ+
    17. Re:That old chestnut? LOL. by Giant+Electronic+Bra · · Score: 3, Interesting

      FORTH RULES! I wrote a FORTH the other day inside my Java Unit test environment to script all the JavaEE client tests. I mean literally I wrote a forth, it took a few hours. Its missing some features, ain't quite ANSI standard, but its real. No piece of software ever designed in the history of Man is as elegant as FORTH. Does everything perl can do, feature for feature, in 1/10,000th of the code.

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    18. Re:That old chestnut? LOL. by Giant+Electronic+Bra · · Score: 1

      So true. I wrote some pretty large programs in Perl back in the day. It has some excellent features, but today I only just maintain existing software written in perl5, and meanwhile Python adopted all the best things from Perl, and mostly avoids a lot of the worst. Just the fact that there's a real standard for it and alternate implementations puts it on a different level. Perl was far ahead of everything else in 1995, and the Perl community squandered all of that.

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    19. Re:That old chestnut? LOL. by short · · Score: 1

      Because it should be better than Perl 5 and there isn't anything better than Perl 5.

    20. Re:That old chestnut? LOL. by flargleblarg · · Score: 1

      I used Perl 15 years ago but Perl 6 has taken far too long.

      How did you get a copy of Perl 15? I thought that was still 200 years away...

    21. Re:That old chestnut? LOL. by Anonymous Coward · · Score: 0

      FORTH RULES! I wrote a FORTH interpreter the other day inside my Java Unit test environment to script all the JavaEE client tests. I mean literally I wrote a forth interpreter; it took a few hours. It's missing some features, ain't quite ANSI standard, but it;s real. No piece of software ever designed in the history of Man is as elegant as FORTH. Does everything perl can do, feature for feature, in 1/10,000th of the code.

      FTFY

    22. Re:That old chestnut? LOL. by shutdown+-p+now · · Score: 1

      Lisp has another problem - there's no language that can do 80% of what it can, but that 80% also happened to be what most programmers don't actually need (or at least not need enough to be worth all the idiosyncrasies that are necessary to enable it).

    23. Re:That old chestnut? LOL. by mfearby · · Score: 1

      Given that it took 15 years to complete the last release, and assuming the same for all the others (unless they do a Firefox and issue a new version every month), then we could expect Perl 200 in the year 4926, and by then our new alien overlords will have mandated the use of something else, I expect (if humans haven't been turned into slaves or food, of course).

    24. Re: That old chestnut? LOL. by Anonymous Coward · · Score: 0

      Actually, your Perl 5 code from 1995 will still work on 2015's Perl 5. It's approach to backwards compatibility is kind of similar to C++'s.

    25. Re:That old chestnut? LOL. by ccanucs · · Score: 1

      Yep - I'm writing in FORTH too. Great language. I also write in Perl 5 - a lot. Won't be moving to Perl 6 any time soon.

    26. Re:That old chestnut? LOL. by Aighearach · · Score: 1

      Right, if you don't care what you use, they do all work. Nobody said otherwise.

    27. Re:That old chestnut? LOL. by Aighearach · · Score: 1

      Sadly, much of that work has shifted to python. I don't like python, because I learned that meaningful whitespace is a bad idea when I was using COBOL.

      Perl's real wart is the hoops to integrate with C. It works great once you get there, of course.

      Text processing these days there are such good libraries for whatever strategy you use, nobody actually has an advantage anymore. Except in cli filters, and then I reach for sed as often as anything.

    28. Re: That old chestnut? LOL. by DrXym · · Score: 1

      I'm referring to perl 6 (& python 3 etc) here as if the context wasn't obvious enough.

    29. Re:That old chestnut? LOL. by Anonymous Coward · · Score: 0

      Maybe there's something you like. And if not, be happy as you are with the programming language you are using now.
      https://wendyga.wordpress.com/2015/12/25/why-would-you-want-to-use-perl-6-some-answers/

    30. Re:That old chestnut? LOL. by Anonymous Coward · · Score: 0

      No, I was asking why you started holding your breath with the Perl 6 announcement, if you knew Perl 5 already? Why was the Perl 6 announcement so big of an issue that you stopped coding in Perl altogether? Why did you choose to wait for Perl 6?

    31. Re:That old chestnut? LOL. by Anonymous Coward · · Score: 0

      Um, why was this given a 4:Interesting? This was supposed to be humor. Note that s/he refers to it as "a FORTH". FORTH is a language, not something you need an indefinite article in front of. If they meant "a FORTH interpreter", then OK, but say that instead.

      Full disclosure: used FORTH for 5 years, hated every millisecond of it, and will never touch it again.

    32. Re:That old chestnut? LOL. by Wendy+Satan · · Score: 0

      It did not take 15 years to complete the last release. During the last 6-7 years, Perl 5 had a yearly new release. At the moment, people are using Perl 5.22, and it has been updated to 5.22.1. Work on 5.24 is on it's way, will be released somewhere next year. Stuff like this is public knowlegde, it's not hidden away.
      http://perldoc.perl.org/perlhi...

  3. Huh... by EmeraldBot · · Score: 2

    It's April Fools already! The older I get, the faster time flies by, I swear...

    --
    "Set a man a fire, he'll be warm for the rest of the night. Set a man afire, he'll be warm for the rest of his life."
  4. Right on schedule? by Anonymous Coward · · Score: 0

    I remember it was supposed to take 18 months and be out for OSCON 2002. What a joke.

  5. Missed the best article quote by Anonymous Coward · · Score: 1

    "This Rakudo release targets those tests (over 120 thousand of them), and passes them all on at least some architectures when the moon is in the right phase."

  6. However... by EmeraldBot · · Score: 1

    In all seriousness, I suppose I'll take a look at it. I'm guessing, however, that Perl 6 is not going to be widely used or liked; it's simply been too long, and Perl isn't even used that much anymore either. That may not impact the dev team directly, but it does mean they're not going to get the support they did with Perl 4 and 5, although I am curious in what they improved during these 15 years.

    --
    "Set a man a fire, he'll be warm for the rest of the night. Set a man afire, he'll be warm for the rest of his life."
    1. Re:However... by DCFusor · · Score: 2

      I use perl daily, still. It's kinda fun, and while no one was looking, it got to be fast and pretty bug-free, along with well, CPAN. Perl 6 evidently tossed the language and runting optimized into one another for the JRI...and fixed what wasn't broke - it really didn't need any more syntactic sugar. I use perl 5.xx in my Lan of things as it's quick to program and is even fairly fast on small cpus - as in raspi and friends. 6 won't match that, and I don't have time to learn new quirks.

      --
      Why guess when you can know? Measure!
    2. Re:However... by alantus · · Score: 1

      My feelings exactly.

      I love Perl for its power. I love CPAN, POD, etc. It is my swiss army tool for everything between quick one-liners and programs with complex data structures.

      The current Perl 5 interpreter is fast and efficient. And I never felt the language itself was missing anything important (although using it for OO is a bit awkward).

      The only thing they should fix in Perl is support for unicode filenames in Windows platforms.

    3. Re:However... by jbolden · · Score: 1

      I agree with your general point but not your details.

      I would bet that more people use Perl 6 than use Perl 4 when it was released. Perl 3 was a very niche language, trying to replace the bash (csh, tcsh) + sed + awk style of scripting. It mostly was poorly known. There was much less Unix in those days, most systems which required admining were still legacy minis. Perl 4 was a huge success and then around the same time the World Wide Web made CGI gateways important which coincided with early Perl 5. ... Perl 6, is coming into a world where the name "Perl" is known, scripting is the dominant form of programming. Perl 6 just has a lot of baggage.

    4. Re:However... by ThePhilips · · Score: 1

      The only thing they should fix in Perl is support for unicode filenames in Windows platforms.

      In the past, I could work it around using the Win32::OLE (with CP_UTF8) and the host scripting interfaces.

      But if I recall correctly, with Strawberry Perl, in couple of cases, I had no problems with the unicode file names.

      --
      All hope abandon ye who enter here.
    5. Re:However... by DuckDodgers · · Score: 1

      I think the fundamental problem with Perl 6 is nothing in the language itself, but the choice of name. Perl 5 and Perl 6 both suffered because a lot of people took a "wait and see" status on whether to adopt either language. If Perl 6 had been Flooby or Rara or something else, Perl 5 users and adopters could have continued on their merry way and Perl 5 would be more popular today.

      In terms of performance, Perl 6 sacrificed a lot of performance at launch by being created as a standard instead of an implementation. But there are already several implementations, and there will be plenty of pressure on the Perl 6 community to optimize for speed. However, I think it's also important to remember that Python is dog slow and wildly popular because most computing tasks people want accomplished can accept a two orders of magnitude performance hit for a solution you can deliver tomorrow versus a C++ solution that nobody will ever bother to write because it's not cost effective. I don't hate Python, mind - I'm just saying that if Perl 6 is just a 'better' (subjectively) Python with similar performance characteristics, that's plenty.

    6. Re:However... by ccanucs · · Score: 1

      Moose "fixes" most of the shortcomings of Perl 5's OO, and, while I still roll my own Perl 5 OO code, I've become more enamored with Moose over time. Not for repeated startup scripts that are invoked 1000s of times because of the startup overhead still, but, for things like Catalyst use it's still great. I'm currently working on a Catalyst project - with Moose at the backend for OO. Good for that.

  7. Yes, Virginia, there is a Santa Claus by Camel+Pilot · · Score: 1

    Well OK that is a bit much... but looking forward to explore Perl 6 in the New Year.

    1. Re:Yes, Virginia, there is a Santa Claus by KGIII · · Score: 2

      I'm sure I'll bump into it eventually. I think Perl comes installed with everything. I don't remember the last time I actually installed it. It probably comes default on Toaster Linux.

      ~$ perl --version

      This is perl 5, version 20, subversion 2 (v5.20.2) built for x86_64-linux-gnu-thread-multi
      (with 51 registered patches, see perl -V for more detail)

      Copyright 1987-2015, Larry Wall

      I'm pretty sure I did not install that. If I need something quick and dirty (I don't) then I guess it's always there. I'd remove it but I know that if I do, I'll think of a reason to use it. I'm trying to learn Python now. It has been too long since I've done much coding - except in PHP and not even that for seven or eight years. I am in the process of picking it back up and that means relearning a bunch of stuff and a whole lot of new stuff. Perl will be in there eventually - even if just a refresher.

      --
      "So long and thanks for all the fish."
    2. Re:Yes, Virginia, there is a Santa Claus by Cochonou · · Score: 1

      perl is a requirement on many linux distributions. Which means they will not work without it.

    3. Re:Yes, Virginia, there is a Santa Claus by KGIII · · Score: 1

      I kinda figure something is still using it. Damned if I know what.

      --
      "So long and thanks for all the fish."
  8. Hmm. by Anonymous Coward · · Score: 0

    Do the Duke Nukem guys have to pay their bet that this would never ship?

  9. Disconnected from the target market by Anonymous Coward · · Score: 0

    Well I have to say that the language developers seem to be unaware that the reason that most of the programmers are using Perl up to this point is that the companies that they work for, the coworkers they work with, and the code base they work on is kinda stagnate and quite resistant of change... even if a change would be great improvement. Think of taking the slow rate of adoption of Python 3 and multiply that by twenty or so. I wouldn't expect the IT departments of these companies that still pay Perl programmers would install the new version anytime soon. Let's face it, most of the small and more nimble contractors or shops that have the ability to adopt change have already moved on a while ago anyways.
    AC because I'm one of those that get paid to write in this stuff still.
    Perl RIP

    1. Re:Disconnected from the target market by Anonymous Coward · · Score: 0

      That is so true. Perl is still heavy used by a lot of sysadmins, but I've yet to see a substantial amount of sysadmins that know what happened after Perl 5.8. A lot of them even writes code like it's still Perl 5.6.

  10. PHP vs Perl by darkain · · Score: 1

    How much you wanna be that because PHP just had their first major version increase in over a decade just this very month is the only real reason that Perl decided to do the same? Now I'm personally not trying to advocate or attach either language here, just pointing out the interesting comparison and timing.

    1. Re:PHP vs Perl by klapek · · Score: 1

      Here we go again: perl6 is not a major version of perl5. It's a completely different language. The last major version of perl5 is 5.22.0 released 2015-Jun-01(http://perldoc.perl.org/perlhist.html). The strongest point I have against perl6 is it's confusing name and the fact it's ruined the perl work market.

    2. Re:PHP vs Perl by dougmc · · Score: 1

      and the fact it's ruined the perl work market.

      How has it ruined the perl work market?

    3. Re:PHP vs Perl by Anonymous Coward · · Score: 1

      I don't think ruined is the right word. It did however make the suites think that perl was dead. Seen a lot of projects where they wanted to rewrite perfectly good perl5 code into something else. Not because it did anything wrong but because perl6 was taking too long and they didn't wanted to invest more into perl5 which they thought was EOL. Perl 5 is still under heavy development with a new major release every year, often full with new stuff. Perl 5 is not dead and will continue to live on and be developed for a long time, but it's lousy marketing. We may celebrate that Perl 5.22 is finally out and we can start migrating all that old Perl 5.20 code, but for the untrained eye it sounds like just a minor bugfix release. I would have made so much more sense to call Perl6 something completely different and just let Perl 5.10 be Perl 6.0.

    4. Re:PHP vs Perl by klapek · · Score: 1

      By making people think perl5 is obsolete and waiting for perl6. In the meantime(15 years!) many gave up waiting and gave up perl all together. Can you name one company that began a new perl project in the last 5 years?

    5. Re: PHP vs Perl by Anonymous Coward · · Score: 1

      Well that's just fucking stupid

    6. Re:PHP vs Perl by Anonymous Coward · · Score: 0

      Can you name one company that began a new perl project in the last 5 years?

      How the fuck do you expect people to know about every company's internal projects?

    7. Re: PHP vs Perl by Anonymous Coward · · Score: 0

      So... no? Not even 1? You don't have to know them all, just one...

    8. Re:PHP vs Perl by jbolden · · Score: 1

      I think that's a completely inaccurate apologetic. And I say that as a guy who wrote a lot of Perl 5 code during the 1990s. Perl 6 was born from the Perl 5 community's desire to make major changes to Perl. If it had come out in 2002 it would certainly have been "the next major release of Perl". It's just that the community bit off way more than it could handle, failed repeatedly...

      No question the Perl work market was harmed by the Perl 6 fiasco. Failure to build a new version in a timely fashion creates an opening for competitors. Quark, Visual Basic, Flash, Common LISP ... suffered the same fate.

    9. Re: PHP vs Perl by Anonymous Coward · · Score: 0

      Disney

    10. Re: PHP vs Perl by Anonymous Coward · · Score: 0

      And yes, I'm actually on the project. Perl 5 works great, and experienced coders can write elegant code just fine with it.

    11. Re: PHP vs Perl by Anonymous Coward · · Score: 0

      You have to know them all to claim that none of them are in Perl.

    12. Re: PHP vs Perl by Giant+Electronic+Bra · · Score: 1

      I do have some bitches though. Its impossible to write a good code analyzer or even syntax highlighter for perl5 code. There are elements of the syntax that are obtuse even for people like me that have written literally millions of lines of perl code over 20 years. And aren't you really sick and tired of writing my ($self,$foo,$bar,$baz) = @_; YET? I know I sure am!

      I write extremely clear and concise OO code in perl, but its STILL difficult to understand at a glance.

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    13. Re: PHP vs Perl by Anonymous Coward · · Score: 0

      That depends on which OO library you use.

    14. Re: PHP vs Perl by gnork · · Score: 1

      I And aren't you really sick and tired of writing my ($self,$foo,$bar,$baz) = @_; YET? I know I sure am!

      I for one will never get tired of writing: bless $self

      --
      Earth is a beta site.
    15. Re:PHP vs Perl by DuckDodgers · · Score: 1

      I wrote the same thing further up thread. Agreed on all counts.

    16. Re: PHP vs Perl by ccanucs · · Score: 1

      Nagios

    17. Re:PHP vs Perl by Anonymous Coward · · Score: 0

      Well, of course you most certainly would only know this if its your own company.

      And yes, in my company we have started new Perl projects in the last 5 years.

    18. Re:PHP vs Perl by b2gills · · Score: 1

      I'm sure that one of these is less than 5 years old: Lacuna Expanse, Duck Duck Go, Geekuni, Questhub, The Game Crafter, Treasurer's Briefcase

    19. Re: PHP vs Perl by b2gills · · Score: 1

      The most recent version of Perl5 has experimental support for subroutine signatures. ( I doubt it will change incompatibly before it is no longer experimental. )

    20. Re:PHP vs Perl by klapek · · Score: 1

      treasurersbriefcase.com is 403, geekuni is perl related. Duck Duck Go is with us since 2008. The others are quite obscure.

    21. Re: PHP vs Perl by Giant+Electronic+Bra · · Score: 1

      That I can at least understand. If Perl was a PURE OO language it would be just built in, but given the way its an incremental feature that you can ignore, then it makes sense that there's SOME sort of syntactic "this is now an instance" thing.

      This IS one thing that perl6 fixes, you have a more regular argument syntax. Of course there are some really, IMHO, stupid choices as well, like why do I have to go find other instances of the same sub/method and rename them 'multi' just because I now have 2 signatures? Or why is there sub and method as separate things in the first place, and WHY is 'sub' changed mysteriously to '->' when the method is anonymous? There's actually a LOT of other similar inconsistencies and bad code maintenance choice things I noted in just a cursory survey of perl6.

      I don't know all the tricks, but it seems like several of the good features of perl5 went away, and several poorly considered or overly thought new things of more marginal use appeared. Simple scripts may be a little bit cleaner in perl6, I'm not sure, but I don't think overall its a drastic improvement over perl5. Some more advanced things like currying or implicit iteration MAY be a little more straightforward, but not by much. I'm having a hard time seeing what was gained, apart from function parameters. Couldn't we have just gotten those in 2002 and called it a day?

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    22. Re: PHP vs Perl by Giant+Electronic+Bra · · Score: 1

      Well, perl has had a form of subroutine signature since forever, you can put sigils in quotes after the name of the subroutine, like sub fooBar($$@) (I think you can even do something like fooBar($foo, $bar, @baz) but the names don't matter). ALL that does is allow the compiler to let you elide the parens when you call the subroutine, like "fooBar $foo, $bar, @baz;" instead of "fooBar($foo,$bar,@baz);" which is not really the same thing at all, you still need the silly local variable incantation at the start of every subroutine. Its just some extra noise that could profitably be removed, and frankly being able to call subs without '()'s around the arguments is NOT a feature, its an excuse for bad code. If it enabled some really amazing syntactic wizardry I might shrug and say 'whatever', but it really doesn't.

      Anyway, maybe 5.13 or whatever is the next perl5 has something else in mind for this syntax, I don't know. Frankly perl became too limited for my ambitions. Its a fine language for 50-100 line utility programs and modules, but there are tools out there that scale MUCH better and eventually you find that its just not cost-effective to stick with perl for larger projects. Not that I would use Python, Ruby, or PHP for any of those either, but for many of the same reasons. Maybe in the end that's why perl6 doesn't really excite me anymore. I was interested 10 years ago, but we've moved on since then. People doing what I did in say 2001 or so MIGHT find perl6 to be a slight improvement, maybe.

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    23. Re: PHP vs Perl by skids · · Score: 1

      Why do I have to go find other instances of the same sub/method and rename them 'multi' just because I now have 2 signatures?

      So you can get compiler warnings when you accidentally try to shadow an 'only' sub definition in the same scope when you are not using multis.

      why is there sub and method as separate things in the first place

      Because calling conventions are customized to OO in methods -- you have an invocant, and unknown named parameters are, by default, ignored so you can easily subclass.

      and WHY is 'sub' changed mysteriously to '->' when the method is anonymous

      anonymous subs using "sub" still work. '->' is a generic closure syntax which you may prefer if you like it.

      I'm having a hard time seeing what was gained

      It's as much about what was lost than what was gained -- Perl 6 leaves behind a lot of the things that demanded a spirit of loyalty to put up with, like variant sigils, so it will be less irritating to a wider audience. The whole language is much more self-consistent, and things that would have required a complete overhaul of Perl 5 to implement have not had to contend with the obstacle of backwards compatibility.

    24. Re: PHP vs Perl by Giant+Electronic+Bra · · Score: 1

      So you can get compiler warnings when you accidentally try to shadow an 'only' sub definition in the same scope when you are not using multis.

      No other language needs this. In both perl6 and Java for instance it is illegal to have 2 functions of the same exact signature in the same scope, and multi doesn't change that (how would it). NOTHING is gained by multi, except added syntactic complexity and the need to revise existing code when adding a new method/function that has the same name as an existing one, which is fairly common. By itself this is trivial, but perl6 commits this same sin again and again in different ways, meaning you have remember many non-value-adding syntactic rules. Its just poor language design and smacks of some sort of 'ashcan design' where everyone stuck their nose in and added an extra bad idea.

      why is there sub and method as separate things in the first place

      Because calling conventions are customized to OO in methods -- you have an invocant, and unknown named parameters are, by default, ignored so you can easily subclass.

      But again, other languages don't need this, and neither does perl6. If such calling conventions are 'good' then why not use them for all subroutines? Surely they aren't better for methods than they are for other function calls. Why not allow either style of call for the same function without needing extra syntactic noise? Surely a compiler can distinguish one type of invocation from the other! This again removes an entire extra keyword and in fact would also remove other related oddities.

      and WHY is 'sub' changed mysteriously to '->' when the method is anonymous

      anonymous subs using "sub" still work. '->' is a generic closure syntax which you may prefer if you like it.

      OK, fair enough, I didn't see where 'sub' was still supported in this context, but that's fine. Personally I find '->' ugly and cryptic, but to each his own!

      I'm having a hard time seeing what was gained

      It's as much about what was lost than what was gained -- Perl 6 leaves behind a lot of the things that demanded a spirit of loyalty to put up with, like variant sigils, so it will be less irritating to a wider audience. The whole language is much more self-consistent, and things that would have required a complete overhaul of Perl 5 to implement have not had to contend with the obstacle of backwards compatibility.

      Well, I certainly understand that perl5's sigil-based 'casting' is obtuse until you get used to it. I might become comfortable with perl6 in time, if I have some reason to bother. That's a big question though at this point. What exactly IS the argument for perl6? It certainly doesn't seem to bring anything radically new to the table. I doubt its simpler and cleaner than Ruby for instance, which I've also never really used, but would probably find more compelling right now today if I was told I needed to pick a modern scripting language (and being no fan of JavaScript). perl6 is certainly WAY late to the party. I doubt it is currently anything near as optimized as perl5, Python, Ruby, etc. It doesn't appear to have any revolutionary multi-threading/parallel processing magic that other languages don't have. It certainly lacks the sort of advanced features and concept that Erlang and similar languages present.

      Honestly, its a bit sad. I liked the perl community pretty well, but I guess the world moves on. perl5 seems unlikely to acquire portability, usable multi-processing, or other really advanced features. Its still a decent language with wide support, but it seems almost inevitably doomed to slow obscurity in its little ever-shrinking niche. perl6 seems unlikely to thrive at this late juncture. I guess Ruby and Python have both long since absorbed the lessons of perl, as have other parts of the IT world. Certainly CPAN was a huge influence far beyond scripting languages. The world is better for having had perl, but I guess nothing lasts. perl6 seems more like a footnote or epitaph than something really new to me. Sorry if that's a glum assessment to a perl6 supporter, but I was one too, in 2003 or so...

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    25. Re: PHP vs Perl by skids · · Score: 1

      and the need to revise existing code when adding a new method/function that has the same name as an existing one

      Let's be precise: the need to add one multi to the one only sub that was allowed before you made it a multi. Compared to the benefits of being able to close the definition of the sub for the optimizer to inline it under more circumstances, this is a minor incovenience.

      If such calling conventions are 'good' then why not use them for all subroutines?

      Because different calling conventions are better at different things. Generally in he style that uses subs, you do not want an unknown named parameter to be ignored, but when inheritance is involved, you do.

      It doesn't appear to have any revolutionary multi-threading/parallel processing magic that other languages don't have.

      Other languages have hyper/race operators and composeable concurrency primitives baked into the core? News to me.

      Time will tell. The same arguments you make could have been levied against, for instance, go. There's enough dissatisfaction with currently available languages that new ones crop up all the time. Perl 6 has aimed at producing something that will gain more users fed up with the status quo than it will lose to alternatives, and I think as it stabilizes, that objective will have been achieved. Unless it gets pushed in the media as a fad, all languages have to go through an adoption curve and this is the healthier way for it to grow, because it allows more feedback to be generated from less aggregate frustration.

    26. Re: PHP vs Perl by Giant+Electronic+Bra · · Score: 1

      Oh, "let me design my own language, it will be the best" is just programmer peen basically. There's a very slow gradual advance, as well as slow changes in the usage patterns for code, which means that SOME new languages add some small increment to coding practices and whatnot, but I'm not seeing where perl6 does that. It doesn't top Erlang or even ANCIENT versions of Scheme or LISP in concurrency, and it doesn't top other modern scripting languages in any other respect AFAICT.

      As for your other comments, the optimizer can't tell when there are two overlapping call signatures? Really? Who wrote that? They spent 12 years on it and that's as far as they got eh? Wow! I disagree that different calling conventions are good. It requires remembering how to do basically the same thing in multiple ways. If named parameters are best, they're best. If you need some to be optional or mandatory, then provide a syntax for that. As for standard positional arguments, you can always pass a NULL as an argument, always could and always will be able to do that.

      --
      "Malo periculosam, libertatem quam quietam servitutem." -- Jefferson
    27. Re: PHP vs Perl by Anonymous Coward · · Score: 0

      Well, perl has had a form of subroutine signature since forever, you can put sigils in quotes after the name of the subroutine, like sub fooBar($$@) (I think you can even do something like fooBar($foo, $bar, @baz) but the names don't matter). ALL that does is allow the compiler to let you elide the parens when you call the subroutine, like "fooBar $foo, $bar, @baz;" instead of "fooBar($foo,$bar,@baz);" which is not really the same thing at all, you still need the silly local variable incantation at the start of every subroutine.

      You're talking about prototypes there, not signatures, and that's not all they do: they also enforce list/scalar context on the parameters. They don't make the () optional, they just give perl more information to decide what's part of the sub call and what's not. If you define the sub before you call it, you can leave out the () even when you don't use prototypes.

      Prototypes are ignored for method calls, and if you're passing any parameters to a method you need the () so if you're mostly writing OO code then prototypes are not very relevant.


      $obj->method;
      $obj->method('x','y','z');

      perl 5.20 included signatures:


      sub whatever($x, $y, $z) { ... }

  11. Unicode characters in code by spauldo · · Score: 2

    One thing that caught my eye was this:

    Non-digit unicode characters with a numeric value (½ and such) can now be used for that numeric value

    and

    Provide tau constant (also: )

    (There's a Unicode tau there that slashdot won't pass)

    I've seen this in Emacs LISP, but I haven't seen it elsewhere (granted, I mostly use older languages...). I imagine non-ASCII characters in code are going to be a point of contention among developers.

    Related:

    Superscripts can now be used for integer powers

    I haven't payed much attention to Perl 6 (I use Perl 5 for a lot, though), but now I'm looking forward to playing with this.

    --
    Those who can't do, teach. Those who can't teach either, do tech support.
    1. Re:Unicode characters in code by Waffle+Iron · · Score: 1

      So whereas in other programming languages, you have to waste 200 milliseconds typing combinations of characters like "1/2" or "**2", now you can instead waste five minutes drilling down through menus like "Edit->Insert->Other->Symbol...", then searching for the appropriate page out of 50 entries in a drop box like "Smileys", "Electrical Symbols", "Arrows", "Connectors", ahhh, there it is: "Mathematics (1 of 7)", then scan a grid of about one hundred icons and finally click on your eye-candy symbol.

      Or alternatively, you could use and editor that infuriatingly auto-inserts the symbols the way a Microsoft Office app would, so half the time when you don't want it the magic substitution, you have to stop, back up, and retype it. Either way, you've probably lost your train of thought.

    2. Re:Unicode characters in code by fahrbot-bot · · Score: 1

      One thing that caught my eye was this:

      Non-digit unicode characters with a numeric value (½ and such) can now be used for that numeric value.

      Whew! The lack of that has really hindered me in writing the - literally - tens to hundreds of thousands of lines of Perl 5 code I've written over the years. Now I can get to work! (Still doing everything one can do (perhaps differently) in Python, btw.)

      --
      It must have been something you assimilated. . . .
    3. Re:Unicode characters in code by John.Banister · · Score: 1

      For the small number of such symbols I use regularly, I make up a text file (called "insert symbols") that has these symbols so I can copy & paste them where I need them. I wouldn't use them to replace **2, but I use the little circle to replace "Degrees" when talking about temperatures very regularly.

    4. Re:Unicode characters in code by Anonymous Coward · · Score: 0

      On Linux, just pressing 1 2 gives me ½. Likewise > > gives me . If you use a sensible system for these characters, they're actually quite easy to use (not that I'm terribly likely to use ½ in code, though 3 is rather cute).

    5. Re:Unicode characters in code by DuckDodgers · · Score: 1

      Perl 6 supports both. You can use U+00AB or (that's "less than", "less than", if the ASCII characters get swallowed by Slashdot). No time wasted.

    6. Re:Unicode characters in code by Anonymous Coward · · Score: 0

      Perl 6 has unicode notation when sensible, but it's ALWAYS accompanied by an ASCII "texas" notation (bigger).

    7. Re:Unicode characters in code by Anonymous Coward · · Score: 0

      That should be <compose-key> 1 2 and <compose-key> > >

    8. Re:Unicode characters in code by Anonymous Coward · · Score: 0

      <
      You're welcome.

    9. Re:Unicode characters in code by Anonymous Coward · · Score: 0

      No, that's not how you type them. There's Compose Key sequences and with the same amount of keystrokes you get much more readable code. Perhaps, in the future, if you think something is ridiculous, you'll first think about whether you understood it correctly.

  12. Erlang 2.0 /Psycho bitch!!! by Billly+Gates · · Score: 3, Funny

    Yo yo hipster web developers. The new rockstar language is Erlang reborn aka Outlaw Techno Psycobitch which you can write hipster low 16 color flat modern impress your cat applications and websites!!

    Perl and Ruby on rails is sooo last decade man for crusty developers

  13. Some more information by bads · · Score: 4, Informative

    The Perl 6 Architect writes about the 7-8 years work put in to get this far at https://6guts.wordpress.com/20...

    "In the coming days, weâ(TM)ll also produce a Rakudo Star release â" which consists of the compiler along with documentation and a selection of modules â" and that will also have an MSI, to make life easier for Windows folks."

    There will also be perl 6 speedups in a series of monthly releases next year.

    A good starting point with download instructions and docs links is
    http://perl6.org/downloads/

    Have fun!

  14. Just read some of the spec by bytesex · · Score: 1

    I'm not sure I like all that simplification. I mean, I kinda liked it when @array[ 1 ] and $array[ 1 ] had different results (but worked on the same array).

    --
    Religion is what happens when nature strikes and groupthink goes wrong.
    1. Re:Just read some of the spec by cruff · · Score: 1

      I'm not sure I have found a single document that I would call a language specification. They seem to say the language will be officially defined by a bunch of unit test definitions.

    2. Re: Just read some of the spec by Entrope · · Score: 1

      If you can't remember the spec implied by 120,000 unit tests, maybe Perl 6 is not the language for you.

      By which I mean, maybe it's not the language for anyone who isn't one of the core developers.

      While I once eagerly waited for Perl 6 to be done, its developers seem too busy adding regex modifiers and questionably valuable parser support for Unicode fractions and superscripts (maybe next they will let developers provide overloading for subscript code points?) to explain when the language is a compelling alternative to all the other text-oriented scripting languages in the world.

    3. Re:Just read some of the spec by Anonymous Coward · · Score: 1

      I'm not sure I have found a single document that I would call a language specification. They seem to say the language will be officially defined by a bunch of unit test definitions.

      Perl6 Design Docs: https://design.perl6.org

    4. Re: Just read some of the spec by Anonymous Coward · · Score: 0

      If you can't remember the spec implied by 120,000 unit tests, maybe Perl 6 is not the language for you.

      By which I mean, maybe it's not the language for anyone who isn't one of the core developers.

      A strong test suite is a bad thing?

      How many test cases would be implied by Java 8 and all the Apache Commons objects? How complete is the existing test coverage?

      The Perl6 language specification includes support for simple concepts (like gradual typing) that require some serious testing to ensure compatibility. For example this one feature needs testing with how methods, subroutines and anything else similar handles various input types in various parts of the signature. Furthermore, every collection types need to be tested to show that they handle types correctly.

      Furthermore, Perl6 was intended to be a rigorously defined language, instead of another scripting language with "it is what it does" as a specification. In fact, from the beginning, the plan was to separate the design spec from the implementation. There have been several implementations of Perl6 over the years, such as Pugs, Niecza, and Rakudo. Without a very thorough test suite, how can I as a developer be sure that any given platform is a really a good Perl6 compiler?

    5. Re:Just read some of the spec by Anonymous Coward · · Score: 0

      What were the different results?

    6. Re:Just read some of the spec by cruff · · Score: 1

      Perl6 Design Docs: https://design.perl6.org/

      Yes, that is exactly the page which led me to make my comment.

  15. Congratulations! by Anonymous Coward · · Score: 1

    Well, let me be the first to say - that's really cool! No matter what your favorite language is, congratulations to the Perl 6 team are in order for their hard work and perserverance.

  16. Sme old same old by edittard · · Score: 1

    Why "Now" after a comma?

    --
    At the bottom of the /. main page it says 'Yesterday's News'. Well they got that right.
  17. Perl Festivity Levels by TheRealHocusLocus · · Score: 4, Funny

    repost

    Perl Festivity Level 1: Developers and users have gathered to nibble hors d'oeuvres and chat amiably with each other about the Modern Perl Renaissance. With every sip of their drinks Perl seems ever more striking. Some are gathered around the upright piano improvising songs that proclaim how it is faster, neater, and sharper than ever before with its asynchronous APIs.

    Perl Festivity Level 2: Everyone is talking loudly -- sometimes to each other, and sometimes to nobody at all. Perl seems even better. Perl Monks are patiently explaining syntax and style to potted plants and other nearby objects. Around the piano people are feeling fun and flexible, just as programming in scripting languages used to be. Someone is crooning a bawdy ballad where a couple of inexperienced DOM and CSS selectors encounter a very supportive bundled development server.

    Perl Festivity Level 3: Monks are arguing violently and defrocking one another over nested do...until loops that bail on exceptions. People are gulping down other peoples' drinks, placing hors d'oeuvres in the upright piano to see what happens when the little hammers strike as everyone bawls "Got my Mojolicious workin' ... but it don't work on Python!" They have lost count of their drinks, and the world is harmonious with blissful adherence to modern interfaces and standards.

    Perl Festivity Level 4: All the guests, hors d'oeuvres smeared all over their naked bodies are performing a ritual dance around a burning heap of tables and chairs in celebration of postfix dereference syntax, subroutine signatures, new slice syntax and numerous optimizations. The piano is missing.

    ~~ with apology and deference to Dave Barry

    --
    <blink>down the rabbit hole</blink>
  18. http://www.perl.org/ by Anonymous Coward · · Score: 1

    Until it gets here

    https://www.perl.org/

    I ain't bothering.

    1. Re:http://www.perl.org/ by Anonymous Coward · · Score: 0

      That's the site for Perl 5. Perl 6 is a different language and has its own website.

    2. Re:http://www.perl.org/ by Anonymous Coward · · Score: 0

      Until it gets here
      https://www.perl.org/
      I ain't bothering.

      That's the site for Perl 5. Perl 6 is a different language and has its own website.

      So, he's saying that he'll never bother with Perl 6.

      Sounds like a reasonable position to me!

  19. Half-baked "release" by fnj · · Score: 1

    For all those talking about a release of a compiler (but not yet including all modules and other support stuff), rather than the release of the language spec, this is a pretty half-baked "release". It sounds more like yet another dreary development pre-release such as we've been showered with for many years.

    From the Rakudo announcement:
    It passes the full set of language tests on selected architectures when the (quote) "moon is in the right phase".
    "There is still plenty of work ahead for us to improve speed, portability, and stability."
    "We do not claim an absence of bugs or instabilities."
    "We do not claim the documentation is complete."
    "We do not claim portability to many architectures."
    "We do not claim that all downstream software will work correctly."

    Basically all they DO "claim" is that the language spec is finally, FINALLY stable, and there is a first developmental stab at implementing all of it.

    Oh, and the release tag is a bunch of incomprehensible, impossible to remember or pronounce, Cyrillic characters impossible to post here or in any ASCII message. It's just symptomatic of the whole weird alien process associated with Perl 6 from the beginning. I have a lot of respect for a lot of the new stuff in Perl 6, but as a project it is just not very serious.

    1. Re:Half-baked "release" by Anonymous Coward · · Score: 0

      as a project it is just not very serious.

      Sounds like you'd prefer COBOL.

    2. Re:Half-baked "release" by Anonymous Coward · · Score: 0

      The "incomprehensible" name is Christmas, just written in Bulgarian.

      Given Perl's strength in text processing it's only natural to make use of unicode for naming, isn't it? If it cannot be posted here, that says more about the halfbakedness of slashdot.

    3. Re:Half-baked "release" by Anonymous Coward · · Score: 0

      Try 'v6.c' for your release tag. Monthly release are named after cities with active PerlMongers groups.

      For the last 5 years there have been a series of alpha release (aka rakudo star) that have made it possible to write actual code in Perl6 and try out all the proposed syntax and semantics. Recently, v6.b shipped, this was a beta version. Version 6.c is version 1.0 of the Perl6 language.

      Until now, any section of the spec could be rewritten and the language could change out from under you. For example, a few months ago the whole way lists were handled (including some crazy, incomprehensible stuff on when things flatten and when they don't) was completely redone in the Great List Refactor. The end result was that a massive source of suck was removed from the language and replaced with comprehensible rules. It also broke a lot of existing code. The GLR occurred without any deprecation cycle.

      What 6.c means, is we have reached 1.0 status. Future breaking changes will occur only with a sane deprecation cycle.

  20. I had hair when that mattered. by DougReed · · Score: 1

    I wonder if Larry Wall even still uses PERL...

    1. Re:I had hair when that mattered. by John+Bokma · · Score: 1

      He never did.

  21. Congratulations! by Anonymous Coward · · Score: 0

    Regardless of what language is your favourite.

  22. After 15 years of failure, not work. by Anonymous Coward · · Score: 4, Interesting

    Perl 6 has not been released "after 15 years of work". It has been marred by one disaster after another. It has been released after 15 years of failure.

    Those who have been following its development then entire time will remember the Parrot virtual machine shenanigans, which wasted many years, and prevented a usable Perl 6 implementation from becoming available.

    Then there was the Pugs implementation of it, which actually seemed slightly promising at first. That, of course, turned into a disaster when the lead programmer decided to change his gender. (I'm not even joking!)

    There's also Perl 6's absurd logo, which renders Perl 6 unusable in any serious environment. We'd be laughed at if we showed the Perl 6 home page to managers, executives or clients when advocating for the use of Perl 6. They'd think we were pulling their leg by using a language with such a childish logo.

    Lately the focus has been on Rakudo which has taken years to produce something even minimally useful. I've read reports that it's slow and forces you to use some obscure MoarVM they've created (this sounds to me like they're on the road to another Parrot-style failure!) or the JVM.

    Perl 6 has been a shameful episode in the history of programming languages. It's even worse that it has permanently tainted the Perl name.

    1. Re:After 15 years of failure, not work. by Anonymous Coward · · Score: 0

      https://www.google.com/search?q=virtues+of+failure

    2. Re:After 15 years of failure, not work. by Anonymous Coward · · Score: 0, Insightful

      Then there was the Pugs implementation of it, which actually seemed slightly promising at first. That, of course, turned into a disaster when the lead programmer decided to change his gender. (I'm not even joking!)

      Yuk, you emphasize some of your misplaced transphobia just to express you are disappointed by a programming language... That's really hurtfull so keep it for yourself !

    3. Re:After 15 years of failure, not work. by Anonymous Coward · · Score: 1
    4. Re:After 15 years of failure, not work. by Anonymous Coward · · Score: 0

      Rakudo also runs on the JVM. In fact i was ported to the JVM before MoarVM was created.

      Rakudo was spun off from the Parrot project, and continued to support it as a backend until recently.

    5. Re:After 15 years of failure, not work. by b2gills · · Score: 1

      Actually Camelia ( the butterfly logo ) is a test to see if we want you in the community.
      You have failed the test.

    6. Re:After 15 years of failure, not work. by Anonymous Coward · · Score: 0

      A programming language implementation "turned into a disaster" simply because of the gender of its creator? Not because of any technical factor? You live in a different world to me, that's for sure.

    7. Re:After 15 years of failure, not work. by Anonymous Coward · · Score: 0

      Are you fucking illiterate? The GP mentions the JVM!

      I've read reports that it's slow and forces you to use some obscure MoarVM they've created (this sounds to me like they're on the road to another Parrot-style failure!) or the JVM.

      But using the JVM isn't something to be proud of. It's better not to force users to use one of those goddamn virtual machines.

    8. Re: After 15 years of failure, not work. by Anonymous Coward · · Score: 0

      turned into a disaster when the lead programmer decided to change his gender. (I'm not even joking!)

      What kind of joke would that be? You got her pronoun wrong. And what have your gender issues to do with the quality of a programming language?

    9. Re: After 15 years of failure, not work. by Anonymous Coward · · Score: 0

      Instead of getting your panties twisted, read the fucking Wikipedia articles that the GP linked to.

      Despite these factors, progress on the Haskell implementation stalled in late 2006, as personal issues kept Audrey from devoting as much time to the project as she had in 2005.

      These gender issues apparently prevented work from happening on Pugs, which ended up killing the project.

    10. Re:After 15 years of failure, not work. by skids · · Score: 1

      Seconded. And FWIW pugs came before rakudo-parrot and helped a whole lot giving people something solid to play with to find the weak spots in initial plans.

      Perl 6 does not discriminate, we even hug trolls, come on over.

    11. Re:After 15 years of failure, not work. by Wendy+Satan · · Score: 1, Offtopic

      So, Pugs turned into a disaster after the lead programmer "decided to change his gender". That's quite a lovely way to describe somebody's personal struggle, or an insightful way to describe what happened to Pugs (several parts are used in Perl 6, so not a disaster). She (not a he, but a she) is still followed by many of us, and when anybody in the Perl community talks of her, it is with fondness and respect.

      Next to that, you must really really hate the fact that at least three other transgenders have worked on Perl 6 since the lead programmer you mentioned went away because of personal reasons. It was really a disaster. The other people felt really uncomfortable with us three. Oh, wait, they didn't, hugs everywhere, friendliness galore. That's the nice thing about the Perl community: friendliness, helpful, useful, and above all, mostly not bigoted, mostly no transphobia, mostly no homophobia, and mostly no nasty people that use mean language to demean other people.

      I am also happy that you despise our lovely butterfly Camelia. It was especially designed by Larry Wall himself to appeal to 7 year old girls. But also to see who says nasty things about a programming language that has the courage to have such a logo, because such a person probably will not feel at home in our community.

      Well, the Perl community, and in this case certainly the community of Perl 6 developers, is a community with friendly people. We love Camelia. I feel loved as a person, and it does not seem to matter that I am transgender. Maybe you have to find a place of your own where people appreciate who and what you are. Maybe at some point you will learn to say nicer things.

    12. Re:After 15 years of failure, not work. by jmaslak · · Score: 1

      +1.

      I've been programming in Perl for 20 years. Perl 5 is a great language - it did things 20 years ago that are trendy now - things like closures, functional style (if you want it), autoboxing, etc - certainly these weren't new then, but they were new to many Unix people at the time. It also happens to be extremely concise and evolving (5.22 is quite evolved from 5.0, because, among other things, it has included aspects of Perl 6). Perl 6 is going to be a great language too, as the creator wasn't after creating YACLL (Yet Another C-Like Language), is willing to learn from others, and is willing to embrace techniques others like.

      If you want what exists elsewhere, by all means use that instead. There certainly are a lot of languages out there to choose from, so I'm sure the troll will find one more to his liking. But I'm glad our language and our community (of which I'm a very small part) exists. I'm proud when people are recognized for what they contribute and the vast majority of people who seek to value everyone. It doesn't sound like the troll who started this subthread wants this - that's fine. But those of us who are secure enough in who we are to work alongside very competent programmers from every continent and every gender are happy to continue participating in our community. Oh, we're also happy to have Camelia as our mascot, and hope that it does attract the kind of community that isn't happy with the conventional.

      Of course I suppose The Art of Computing Programming is also a disaster by the standards of trolls. :)

    13. Re:After 15 years of failure, not work. by schamarty · · Score: 1

      +1 from me too.

      As someone who has tried (and failed) several times to learn Haskell, I cannot describe how much I am in awe of someone like Audrey Tang and her sheer brain power.

    14. Re:After 15 years of failure, not work. by MagickalMyst · · Score: 1

      "It's even worse that it has permanently tainted the Perl name."

      There's a workaround:

      #!/usr/bin/perl -T

      --
      Political correctness is really just herd psychology pushed by insecure people who desperately seek social conformity.
    15. Re:After 15 years of failure, not work. by Anonymous Coward · · Score: 0

      By your terms, failure does not entail work. Truthfully, failure often entails some of the most important work. It is foolish to discount the value of failure.

    16. Re: After 15 years of failure, not work. by Anonymous Coward · · Score: 0

      They were *different* personal issues from what you're assuming. Hope this helps.

  23. In other news... by Anonymous Coward · · Score: 0

    After 15 years of solid work, a new computer card reading console has been released.

  24. Perl6 greatest failure by ThePhilips · · Score: 1

    Over the years of using Perl5 I have realized its greatest shortcoming: I have to type $/%/@ characters too often, what sometimes gets me - especially if I try to do something OO in Perl.

    I have looked (again) at Perl6 recently, and was appalled to see that it used even more of punctuation than the Perl5.

    As a way forward for Perl5, a special mode which allows to omit the $/%/@ qualifiers would be really nice. After all, Perl already has the "bareword" error handling: it shouldn't be too hard to make the qualifier optional.

    --
    All hope abandon ye who enter here.
    1. Re:Perl6 greatest failure by Anonymous Coward · · Score: 0

      Don't like sigils?

      $ perl6
      > my \array = 1, 2, 3
      (1 2 3)
      > say array
      (1 2 3)
      > my \hash = a => 1, b => 2
      (a => 1 b => 2)
      > hash
      (a => 1 b => 2)

      There you go.

    2. Re:Perl6 greatest failure by ThePhilips · · Score: 1

      Using references for this?... Perl6 is crazier than I thought.

      --
      All hope abandon ye who enter here.
    3. Re:Perl6 greatest failure by b2gills · · Score: 1

      Why would you think that is a reference? We're talking about Perl 6 not C. That is a term definition, which is a bit like a constant alias, or static single assignment.
      One of the things I really like about Perl is that when you are reading the code you can instantly recognize the variables.
      Also you can add new operators by simply adding a subroutine. ( In fact all of the operators except the hyper and meta operators are implemented that way in Rakudo )

      sub postfix:<!> ( UInt $n ) is tighter(&[,]) { [*] 2..$n }
      say 5! ; # 120
      say (0..10)>>! ; # (1 1 2 6 24 120 720 5040 40320 362880 3628800)

      say infix:<+> 4, 5; # 9

      my &square = &infix:<**>.assuming(*,2);
      say square 5; # 25


      By allowing you to create new operators it is hoped that you won't do something stupid like use << for IO or + for string concatenation.

    4. Re:Perl6 greatest failure by Anonymous Coward · · Score: 0

      Serious question: are you actually a professional programmer, or is it just a hobby?

      discussions of variable sigils are so far down the list of relevant considerations when discussing a programming language, I can't fathom why anyone who has coded for more than a week would actually bother mentioning them.

    5. Re:Perl6 greatest failure by ThePhilips · · Score: 1

      discussions of variable sigils are so far down the list of relevant considerations when discussing a programming language, I can't fathom why anyone who has coded for more than a week would actually bother mentioning them.

      You probably never had to code couple thousand lines of code in a day, have you?

      Perl5 is otherwise fine language. I'm using it now for more than 15 years, including using it 2 years full-time professionally.

      In the past, on smaller things, Perl's syntax was not as cumbersome. But for newer code, especially OO one, the denser code is just overflowing with the sigils (and dereferences). In the older times, for small/medium stuff, one often resorted to the built-in variables. In OO code, literally everything is a user variable, and a reference more often then not. Sigils and the -> are the most typed characters and are the most annoying ones, since they are hard to type by touch. Modern Perl5 iteration lessen the burden by allowing to skip the -> in more cases than before. But the sigils have remained untouched.

      --
      All hope abandon ye who enter here.
  25. Its better!! by febo11235 · · Score: 1

    Not a Perl veteran, but as some one who have used Perl as one of the main programming languages from last 9 years and has written Production applications in Perl covering more than 50,000 LOC, I am pleasantly surprised to see new Perl 6 Language specification. It is new Perl, with better & cleaner syntax without compromising original Perl identity of being expressive, the language of programmers (more than the language of computers) and many other good things Perl has to offer to generations of Programmers. Even with Perl 5, I never understood so called write only language stamping on Perl, as code written by me has been well maintained in last 9 years by 2 different successive teams to add new features. Ironically, pure Java programmers quickly understood one of my 8 years Perl application code while porting it to Java to gain better performance on multi-core processor in visualized environment (which had good mathematical computations). So its all about programming style, not programming language itself. Seeing new Perl 6, which looks considerably different from Perl 5 and adds many great things to help programmers to write faster and better programs, I think it will be liked by all Perl lovers and sys admins, as well as by new programmers coming in contact with Perl!!

    1. Re:Its better!! by Anonymous Coward · · Score: 0

      If you code in Perl (or anything else) with the same disregard to details as to apostrophes, I can't but thinking that the quality of your code will be awful.

  26. perl6 test by Anonymous Coward · · Score: 0

    is there any perl in http://mattressbern.ir/ !?

  27. I'm sorry for you... by Anonymous Coward · · Score: 0

    Your life must be a hard knock one. My sincere condolences. I hope your future will bring you happiness.

    Meanwhile, I and many others enjoy editors that aren't encumbered by layers of deep obfuscation. Inserting a 1/2 symbol should not (and is not) a half-day projects for me.

    Take a good long look in the mirror, and be the change you want to see in the world. Start using a real editor. Learn how to use vi (or vim). Learn the basics and you'll be twice as efficient as you are now. Learn the complex stuff and you will be an order of magnitude more efficient. Yes, really.

    Ridicule me, it touches me not. Laugh at me, I don't care. I only extend a hand. It is yours to take it or swat it away.

  28. Does anyone even want a new Perl ? by billcopc · · Score: 1

    It really seems like Perl 6 is a solution in search of a problem. Twenty years ago, Perl 5 was literally better than nothing - an intermediate step between shell scripts and C. Ten years ago, it was a scripting tool I could use on otherwise restrictive embedded environments. Today, I only use it because I have this one legacy script I haven't yet bothered to rewrite. At no point have I been on a project and thought "Perl would be ideal for this". It's always been "Aw crap, guess I'll settle for Perl".

    These days, if I can't do something with a Bash script or quick & dirty PHP, then I fire up an IDE and write C/C++/C#, for the simple reason that they can leverage great debugging tools that Perl cannot.

    --
    -Billco, Fnarg.com
  29. dialects by Anonymous Coward · · Score: 0

    Every other computer language is now a dialect of Perl 6.

  30. Yawn by Anonymous Coward · · Score: 0

    1995 called and wants its programming language back. Why is anyone using perl when there's Python

  31. Even when Perl 6 is finally released: still not. by Anonymous Coward · · Score: 0

    for anyone who hasn't read TFA: This is an announcement that a presumed-stable Perl 6 language specification has been released. The compiler itself is considered to be unstable, and their standard of completion is that each test can be made to pass on at least some set-up of at least one architecture (translation: the tests are poorly written, and the compiler barely works)

    There is no claim that all tests pass on any single architecture.

    There is no claim that any test passes consistently.

    There is no claim that any compiler actually works, usefully, *at all*.

    But they're pretty sure they've finished discussing just what exactly the compiler *should* do, in plain english, though probably not in terms of the specifics of what should be tested for.