Slashdot Mirror


The Perl 6 Advent Calendar

An anonymous reader writes "Larry Wall wasn't joking when he said that Perl 6 would be ready by Christmas. Perhaps not this Christmas, but that hasn't stopped a group of people (including head Rakudo developers Patrick Michaud and Jonathan Worthington) from putting together an Advent Calendar, featuring one cool Perl 6 feature every day until Christmas. Topics currently covered include how to get and build Rakudo (the most actively developed and progressed implementation of Perl 6) and the new Metaoperators. For those wondering when Perl 6 will be finished: Rakudo will be having its official 'production release' (dubbed Rakudo Star) April 2010."

160 comments

  1. Word on the street... by ghostis · · Score: 4, Funny

    ... is Duke Nukem Forever is being rewritten in Perl 6.

    --


    Computer Science is all about trying to find the right wrench to bang in the right screw. -T.Cumbo?
    1. Re:Word on the street... by wayland · · Score: 1

      No, I think they're trying to integrate DNF with E17. 

    2. Re:Word on the street... by Fotograf · · Score: 1

      that explains the delay... somebody tried to read the source code

      --
      God's gift to chicks
  2. Coming of the (perl) Messiah by negatonium · · Score: 2, Funny

    Waiting for Perl 6 seems a lot like waiting for the Messiah to arrive. And even when (if) it happens there'll be some people saying "Nope. Not the right one... Keep looking...."

    1. Re:Coming of the (perl) Messiah by Chandon+Seldon · · Score: 3, Insightful

      If you compare the Perl6 timeline to the Haskell timeline, you'll see that things aren't really going all that slowly. Building a good implementation of a complex programming language takes time.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    2. Re:Coming of the (perl) Messiah by convolvatron · · Score: 3, Funny

      yes, but you still haven't explained why perl 6 is taking so long

    3. Re:Coming of the (perl) Messiah by Anonymous Coward · · Score: 0

      Because the first 5 years after its announcement were spent on making RFCs, compiling the results, coming up with ways to incorporate the ideas given in the RFCs etc. The next 2 years were spent writing an implementation in Haskel, Parrot only got far enough long very recently for Rakudo to be started. And Perl 6 has taken just as long as Python 3000 -- Guido changed jobs in 2000 to work on P3000, Larry announced P6 in 2000. I guess complete rewrites of languages just take a very long time?

    4. Re:Coming of the (perl) Messiah by Anonymous Coward · · Score: 0

      It has taken just as long as Python 3000. Guido started work on in it in 2000, still not 'finished'.

    5. Re:Coming of the (perl) Messiah by convolvatron · · Score: 1

      did they really bring it up off haskell? you think they would have
      noticed something

    6. Re:Coming of the (perl) Messiah by Tacvek · · Score: 1

      But Python 3000 is already out, as Python 3.0, while Perl 6 is not. So Perl 6 is taking longer than even Python 3000. Besides, the real reason Guido changed jobs was because Google felt that python was so important to its operations that it could not risk letting development stall, so they made Guido a job offer, with his job being at least in part, developing python. (I have no idea how much work on Google specific stuff Guido does, but I imagine it is probably more than zero).

      --
      Stylish sheet to fix many problems in Slashdot's D3: https://gist.github.com/801524
    7. Re:Coming of the (perl) Messiah by Anonymous Coward · · Score: 0

      There are Perl 6 implementations out right now, none of them have been developed for 10 years like Python 3000 has.

    8. Re:Coming of the (perl) Messiah by Anonymous Coward · · Score: 0

      But Python 3000 is already out, as Python 3.0, while Perl 6 is not.

      The changes from Python 2 to Python 3 are nothing compared to the changes from Perl 5 to Perl 6. It's hardly surprising that it takes a bit longer.

    9. Re:Coming of the (perl) Messiah by ThePhilips · · Score: 2, Insightful

      But Python 3000 is already out, as Python 3.0, while Perl 6 is not.

      Technically, Perl 6 is long time out: specification was out somewhere around 2005. Because the Perl6 isn't a software package (like Perl5), it is a language standard.

      The other question is that there are no implementations of the standard yet...

      And even then, Perl5 serves it's purpose so perfectly, that I personally atm see no real benefits to even toy with Perl6.

      --
      All hope abandon ye who enter here.
    10. Re:Coming of the (perl) Messiah by RDW · · Score: 3, Informative

      'The other question is that there are no implementations of the standard yet...'

      The Rakudo guys have now committed themselves to a useful/usable release (if not a complete implementation of everything in the standard) in Spring 2010 (the target is April):

      http://use.perl.org/~pmichaud/journal/39411

      They intend this to be a release which 'application writers will feel comfortable enough to start using in their projects'.

      This probably helped:

      http://news.perlfoundation.org/2008/05/tpf_receives_large_donation_in.html

      Here's where they are now:

      http://rakudo.org/status

      http://github.com/rakudo/rakudo/blob/master/docs/ROADMAP

    11. Re:Coming of the (perl) Messiah by sqldr · · Score: 1

      well, if you have a quick look through Larry Wall's definitive o'reilly guide on perl, you will find him joculantly using the words "laziness is a virtue of a programmer". He's just being virtuous.

      --
      I wrote my first program at the age of six, and I still can't work out how this website works.
    12. Re:Coming of the (perl) Messiah by Tacvek · · Score: 1

      No argument from me. Perl 6 is a big project. I was just correcting the implication that Python 3000 has been as long time in coming as Perl 6, since it is already here.

      --
      Stylish sheet to fix many problems in Slashdot's D3: https://gist.github.com/801524
  3. PERL went the way of the dodo... by Anonymous Coward · · Score: 1, Funny

    ...it's too late for PERL. The system and kernel engineers chose to stick with C, PHP ran all over it with less cryptic syntax, and all the web 2.0 "me too" morons are now hacking away in Ruby and Python.

    But really, PERL's demise was PHP. Especially since the CLI version of PHP, turning him into a true general purpose language.

    1. Re:PERL went the way of the dodo... by Anonymous Coward · · Score: 0

      PHP as a general purpose language - enabling shit coders to write shitty code to do all kinds of shit.

    2. Re:PERL went the way of the dodo... by outZider · · Score: 1

      Sorry, PHP is still an archaic, over keyworded language. Surefire way to find out if a company doesn't know what they're doing: they use PHP at the command line.

      --
      - oZ
      // i am here.
    3. Re:PERL went the way of the dodo... by pierreact · · Score: 1

      "morons are now hacking away in Ruby and Python"... Oh man. Ruby is great for this kind of stuff, so is, as I heard (ruby user here) python. I used to use perl for those tasks but I found it too messy when writting large programs and ridiculous when it comes to OOP (colors and tastes...). ruby fits my needs, the code is clear and short, it's very maintainable... All I need it here :) I'm happy with it and oh... I used it to automate a 30 nodes cluster all the way. Moron, maybe but the shit works very well in the long run. ;) have a sweet day.

    4. Re:PERL went the way of the dodo... by MathiasRav · · Score: 1

      Is this Funny or Flamebait?

    5. Re:PERL went the way of the dodo... by thetoadwarrior · · Score: 0, Flamebait

      PHP isn't necessarily cryptic but it's just as ugly as PERL.

    6. Re:PERL went the way of the dodo... by edivad · · Score: 1

      ...it's too late for PERL. The system and kernel engineers chose to stick with C, PHP ran all over it with less cryptic syntax, and all the web 2.0 "me too" morons are now hacking away in Ruby and Python.

      But really, PERL's demise was PHP. Especially since the CLI version of PHP, turning him into a true general purpose language.

      Dude, you lost me at PHP.
      Perl IS the most widely spread scripting system on a Unix host, after Shell.

    7. Re:PERL went the way of the dodo... by Anonymous Coward · · Score: 0

      But damn it, it's an unpleasant one to work with. In between shell scripts and python, I've never felt a need to return to it.

    8. Re:PERL went the way of the dodo... by tepples · · Score: 1

      Surefire way to find out if a company doesn't know what they're doing: they use PHP at the command line.

      Unless they have business logic libraries written in PHP, and they want to make sure that the libraries used by the public web site and those used by internal command-line tools have the same behavior. Or to what representation should a library written in PHP be compiled before using it in a command-line program?

    9. Re:PERL went the way of the dodo... by outZider · · Score: 1

      Not PHP.

      --
      - oZ
      // i am here.
  4. This has taken too long by physburn · · Score: 2
    Is it just my memory, or is this over five years on one upgrade. An upgrade with too many changes, apocapses, and major changes in grammer and usage. I'm getting old, and don't really want to relearn my languages just to stay put. So keep on delaying perl 6, and i can safely use perl 5 for the rest of my life.

    ---

    Perl Programming Feed Feed Distiller

    1. Re:This has taken too long by FooAtWFU · · Score: 4, Informative
      Perl 5.10.0 was out this year, and introduced snazzy new features like the defined-or operator and easier state variables. It's not like they've been neglecting the rest of the language, and it's not like it's going to be difficult to activate backwards compatibility.

      I'd worry more about the continuing relevance of Perl in a niche which has come to be dominated more and more by PHP (eww!) and Ruby in recent years. It's not going away, certainly, but its relevance to the future of computing may be somewhat limited despite its technical merit.

      --
      The World Wide Web is dying. Soon, we shall have only the Internet.
    2. Re:This has taken too long by Trepidity · · Score: 5, Funny

      More than that--- Perl 6 was announced 9 1/2 years ago! Even O'Reilly's Perl 6 Essentials is now 6 1/2 years old, and some Perl 6 books are into 2nd editions.

    3. Re:This has taken too long by RDW · · Score: 5, Informative

      Perl 6 is a new language, not just an upgrade. Perl 5 has not been neglected, and continues to receive updates and new features (some of them originally developed for Perl 6). The plan is to continue Perl 5 support and development indefinitely, irrespective of the status of Perl 6. And of course Perl 5 has its own advent calendar, which this year focuses on interesting stuff you can do with various CPAN modules:

      http://www.perladvent.org/2009/

    4. Re:This has taken too long by spottedkangaroo · · Score: 1

      Not at all. Perl6 is not an upgrade of Perl5, which is still being actively developed. Perl6 is a brand new language in the same family. Perl 5.10 is more like what people expect from a language upgrade. It has so many new features it's very much like a new version of the language (and it is).

      --
      Imagine if you weren't allowed to use roads because a bus company complained about your driving 3 times. --skunkpussy
    5. Re:This has taken too long by Anonymous Coward · · Score: 0

      Shipping is a feature. A really important one. Your product has to have it.

    6. Re:This has taken too long by Migala77 · · Score: 1

      Not at all. Perl6 is not an upgrade of Perl5, which is still being actively developed. Perl6 is a brand new language in the same family.

      Then why name it Perl6?
      If it's a different language, give it a different name!

    7. Re:This has taken too long by harmonise · · Score: 1

      Perl 6 is a new language, not just an upgrade.

      Then they should have chosen a new name than use the same name as an established language. By not doing so they have created confusion leading to people thinking, rightly so, that this is somehow an upgrade to the older Perl.

      --
      Cory Doctorow talking about cloud computing makes as much sense as George W Bush talking about electrical engineering.
    8. Re:This has taken too long by Anonymous Coward · · Score: 0, Insightful

      Really? They are building a language from scratch with volunteers. How long should it take them to meet your schedule?

    9. Re:This has taken too long by ThePhilips · · Score: 2, Interesting

      It's not going away, certainly, but its relevance to the future of computing may be somewhat limited despite its technical merit.

      That's silly. Programming languages always were and will always be transient.

      Compare Perl1 to Perl5 (that actually easy since change logs are delivered with every Perl version) and see how language have changed over the time. Like-wise PHP or even C.

      Languages evolve along with tasks they are used to solve. Sometimes obviously a branch of evolution falls off and language becomes a thing of past. And that can happen to any language, because we still can't predict with certainty problems of tomorrow.

      Corollary, niche languages have staying power coming from the niche they occupy. Because niches evolve at much slower pace compared to mainstream technologies, thus has lower risk of being forgotten fast.

      And I personally do not think that Perl has its own strong niche. Probably only a "*NIX shell on steroids" - that's how I use it. As long as *NIX shell would exist, I would use Perl to automate large chunks of logic and information analysis which are hard/impossible to do in shell, but do not justify writing/maintaining a C/C++ program for.

      --
      All hope abandon ye who enter here.
    10. Re:This has taken too long by RDW · · Score: 4, Interesting

      Well, the first line of the first Google hit for 'Perl 6':

      http://dev.perl.org/perl6/

      says:

      "Perl 6 is a new language. Perl 5 and Perl 6 are two languages in the Perl family, but of different lineages. There is no current release schedule for Perl 6."

      Some people, of course, may still find this confusing. These people should use Python :-)

      A longer answer (together with several chapters of new Perl 6 book written by some of the developers) is here:

      http://cloud.github.com/downloads/perl6/book/book-2009-11.pdf

      "Some might ask, 'Why call it Perl if it's a different language?' Perl is more than just the vagaries of syntax. Perl is philosophy (there's more than one way to do it; easy things easy, hard things possible); Perl is custom (unit testing); Perl is architectual edifice (Comprehensive Perl Archive Network); Perl is community (perl5porters, perl6-language). These are things that both Perl 5 and Perl 6 will share to varying degrees. Also, due to Perl's habit of stealing good ideas, Perl 5 and Perl 6 will converge in some areas as Perl 5 borrows ideas from Perl 6 and vice versa."

    11. Re:This has taken too long by jeffstar · · Score: 2, Insightful

      perl and nice don't belong together, especially if you bring CPAN into the sentence.

      When I have some retarded task that has to be done, like taking a web form and inserting the data into a PDF that has to be emailed to a few different people, or retrieving some data via FTP, verifying that it is valid and then updating some excel worksheets and emailing the new plots around as in-line images in an html formatted email, PERL can do it.

      maybe PHP, ruby and python can talk to open office, ms office, do SMTP with TLS or SSL, and insert data into a PDF too. I wouldn't know because once I started with perl I never needed anything else for glue type programs.

      Maybe glue is perl's niche?

    12. Re:This has taken too long by chromatic · · Score: 2, Informative

      Shipping is a feature.

      I'm going to release the 24th stable monthly version of Rakudo Perl 6 in a couple of weeks. How many more releases do we have to release to meet that mythical bar of "shipping"?

    13. Re:This has taken too long by icebraining · · Score: 0, Flamebait

      Python can do all that.

      OpenOffice.org ships with the python scripting language, version 2.3.4.

    14. Re:This has taken too long by Anonymous Coward · · Score: 0

      Being packaged (does anyone besides debian-experimental bother?) and used would be a good benchmark. Your claim of "stable" isn't worth shit.

    15. Re:This has taken too long by chromatic · · Score: 2, Informative

      [Does] anyone besides debian-experimental bother?

      Fedora 12 includes Rakudo Perl 6.

      For comparison, Fedora 13 will likely include Python 3.

    16. Re:This has taken too long by dkf · · Score: 1

      "Perl is more than just the vagaries of syntax. Perl is philosophy; Perl is custom; Perl is architectual edifice; Perl is community."

      And Perl6 is a jump over the shark.

      I've seen snippets of Perl6 and it does indeed look rather different from previous versions of Perl. Does it stand a good a chance of running lots of existing perl scripts without nasty interop goop? If not, it's really another language and should not hang off Perl's coattails. Call it "Rakudo" instead (after all, that name's used right now) and let it find its own way in the world of languages. If instead they'd stuck to being, say, 95% compatible with existing perl scripts then, while it would have constrained their creativity, it would mean they'd be able to pick up on the wealth of CPAN for little extra effort.

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
    17. Re:This has taken too long by wayland · · Score: 2, Informative

      Perl 6 is a specification, not an implementation.  Rakudo is one implementation, but there are others (SMOP springs to mind).  I guess I think that Perl 6 is "the stuff you liked about Perl 5, but more of it".  Oh, and better OO and Grammars.  Mmm, grammars :). 

    18. Re:This has taken too long by wayland · · Score: 1

      > That's silly. Programming languages always were and will always be transient.

      Right.  That's why no-one uses LISP any more.  http://people.mandriva.com/~prigaux/language-study/diagram-light.png

      Oh, wait...

    19. Re:This has taken too long by Anonymous Coward · · Score: 0

      Some people, of course, may still find this confusing. These people should use Python :-)

      Was this supposed to be a joke about the differences between Python 2.x and Python 3.x? ;-)

    20. Re:This has taken too long by Anonymous Coward · · Score: 0

      Makes me wonder if Perl 6 would have been finished already if they wrote it in Perl 5

    21. Re:This has taken too long by polemon · · Score: 1

      I'd worry more about the continuing relevance of Perl in a niche which has come to be dominated more and more by PHP (eww!) and Ruby in recent years.

      I cast Lua at your PHP and Ruby shenanigans!

      --
      EOF
    22. Re:This has taken too long by Draykwing · · Score: 2, Informative

      In addition to what wayland++ said, there's also the fact that the Perl 6 implementation on Parrot, called Rakudo, is intended to be able to mix programming languages with great ease. For example, one syntax that's been bandied about is this:
      use v6;
      # Perl 6 goes here
      {
      use P5;
      # Hey, now I'm writing Perl 5 code!
      }
      # I'm writing Perl 6 again!

      The amazing thing is that the object models will be able to interact, which means that CPAN modules will be trivially usable. That's a different kind of interop from what I showed above, and it's working (to a degree) now. Of course, the languages it works between are Cardinal (Ruby on Parrot), PIR (Parrot's native language), and Rakudo (Perl 6 on Parrot). The syntax is currently like this:
      use opengl:from<PIR>;

    23. Re:This has taken too long by Luyseyal · · Score: 2, Funny

      Maybe glue is perl's niche?

      I'm sure there is a "turning camels into glue" joke in there somewhere.

      -l

      --
      Help cure AIDS, cancer, and more. Donate your unused computer time to worldcommunitygrid.org. Join Team Slashdot!
    24. Re:This has taken too long by eabrek · · Score: 1

      What is apocapses? I read that as apocalypses...

    25. Re:This has taken too long by jkauzlar · · Score: 1

      When I see a post in mono-space font, I always imagine that a robot is talking :)

    26. Re:This has taken too long by ajs · · Score: 2, Informative

      "Perl is more than just the vagaries of syntax. Perl is philosophy; Perl is custom; Perl is architectual edifice; Perl is community."

      And Perl6 is a jump over the shark.

      That's meaningless. You could say that about any new technology (I'm sure someone said it about the DVD).

      I've seen snippets of Perl6 and it does indeed look rather different from previous versions of Perl.

      In some ways yes, and in some ways, no. Perl 4 looked like this:

      require "foo.pl";
      local($foo);
      $foo = 10;

      Perl 5 looked like this:

      package Foo;
      my $foo = 10;

      Perl 6 looks like this:

      module Foo;
      my $foo = 10;

      You tell me which was a larger leap.

      Perl 6 is, conceptually, a massive shift and arguably a language of its own. But in terms of raw syntax and ease-of-learning for current Perl 5 users, it's not as large a change as one might have thought.

    27. Re:This has taken too long by ajs · · Score: 2, Insightful

      Is it just my memory, or is this over five years on one upgrade.

      Perl 6 is not an upgrade to Perl 5.

      This is something that many folks misunderstand, and frankly, it's a failure of the Perl development team to correctly communicate (an open source project with poor PR skills... shocking). Perl 6 isn't a new language either, though you'll find many who will say that it is (even within the project, where it's a sort of shorthand way of interrupting the long conversation that ensues if you don't call it a new language).

      What Perl 6 is is the logical progression of Perl into the realm of modern, highly dynamic language. That means it's drawing on the concepts that come from many popular (and some not so popular) modern languages and blending them in a way that has never been done before. False starts, long implementation paths and re-designs triggered by new insights are par for the course.

      But I want to take exception to the idea that "this has taken too long." How long is too long? If Perl 6 were released 2 days after you died of old age, would that be too long? What about 10 years from now? 5? 2? What's it mean to take too long? There were an abundance of languages that were popular when Perl 6 work started and there will be an abundance of them when Perl 6 lands. What Perl has lost is momentum. Perl 6 will not have the easy conversion of a massive Perl user base to start with, but then Perl didn't have that when it started.

      Perl was a success because it solved a problem. It gave developers a tool for writing simple programs quickly without sacrificing features that they depended on in lower level languages such as binary data, arbitrary size strings and system call access, the three of which did not, as far as I can recall, exist in any other high level language at the time, outside of Lisp and unlike Lisp, Perl felt comfortable and familiar to the average Unix user at the time.

      What will Perl 6 have going for it?

      It will be the first language to give you the rich dynamic OO features of Ruby and Smalltalk, blended with the self-hosted language introspection of Common Lisp and the still-familiar feel of Unix/Linux systems all on a portable and language-neutral VM. Will that be a draw to the same sorts of users that cared strongly about Perl 5? Some yes and some no, but there will be a brand new segment of the programming community that will care strongly about Perl 6 features.

      That's really all that matters, not how long it takes.

    28. Re:This has taken too long by scheme · · Score: 1

      In addition to what wayland++ said, there's also the fact that the Perl 6 implementation on Parrot, called Rakudo, is intended to be able to mix programming languages with great ease. For example, one syntax that's been bandied about is this: use v6; # Perl 6 goes here { use P5; # Hey, now I'm writing Perl 5 code! } # I'm writing Perl 6 again!

      You're seriously calling this a good thing? The ability to fairly easily switch to a very similar but different language in the middle of your code? That sounds like an excellent way to create a maintenance and troubleshooting nightmare.

      --
      "When you sit with a nice girl for two hours, it seems like two minutes. When you sit on a hot stove for two minutes, it
    29. Re:This has taken too long by chromatic · · Score: 1

      That sounds like an excellent way to create a maintenance and troubleshooting nightmare.

      Apply discipline and discretion appropriately, as you would if you worked on a project with HTML, CSS, SQL, JavaScript, a templating system, and some other server-side language.

    30. Re:This has taken too long by Anonymous Coward · · Score: 0

      > That's silly. Programming languages always were and will always be transient.

      Right. That's why no-one uses LISP any more.

      How about reading past the first sentence?

    31. Re:This has taken too long by RevDiaBLo · · Score: 1

      Then why name it Perl6?
      If it's a different language, give it a different name!

      Quite simply, because the guy who first created Perl still wants to call it Perl.

  5. still relevant? by spongman · · Score: 3, Insightful

    from an outsider's view (I have NO perl experience, and i intend to die like that if at all possible) it seems like perl has slowly moved from an ubiquitous scripting language to a fringe research project over the last few years. it reminds me somewhat of the pascal/modula-2/oberon phenomenon. do perl afficionados think that this new version will enjoy the success that its predecessors have had?

    1. Re:still relevant? by bsDaemon · · Score: 3, Interesting

      Perl 6 is NOT Perl 5. Perl 5 has been under active development, introducing several new features. CPAN is constantly getting new libraries and whatnot, which and its possible to throw together quick hacks and elegant solutions in Perl, depending on what you want to do.

      Maybe Perl is more for a systems administration language (it started out that way) than a software development language, but that's what I need, and that's why I like it. Perl combines the features of awk, sed and shell scripting with those of other languages as well, wraps them up in a C-like syntax, but removes all the hard syntactic bits of C that make it harder for processing strings, or just generally cumbersome.

      For me, Perl 5 is perfect. It's pretty much the language that I would have designed if I designed programming languages -- it i well suited to the tasks I do, the problems I tackle, and is expressive in the same way that I think about writing code. That said, I don't give a flying fuck about Perl 6 at all and really have no interest in it at all.

    2. Re:still relevant? by jepaton · · Score: 5, Interesting

      Yes, Perl is still relevant to a number of software developers and systems administrators.

      It is an ideal language for software developers who want to use metaprogramming techniques (code generation; domain specific languages), text processing or data conversion, or automation of software development process. Perl 6 will have a full grammar engine (for parsing - like having YACC/BISON built in) which will make text processing even easier than before. The use of a scripting language for these tasks leaves the source code more accessible than compiled languages, which is an advantage to software developers who can adapt the code more readily than a compiled project.

      Whether Perl 6 will be used much for primary software development I don't know. My day job is C programming for embedded systems where Perl is not suitable. Desktop programming is more likely to be in C++ or C# where the standard libraries are huge and the software development ecosystem is more developed.

      The primary audience for new Perl, in my opinion, is expert software developers who need a powerful/succinct language to implement solutions to problems in the manner they think. Perl 6 therefore supports just about every programming paradigm known to mankind. What makes Perl great for software gurus is what makes it an awful language for programming newbies.

      I will be learning Perl 6, not because I will use it much, but because I will discover new ways to think about problems. Oh, and it'll be fun.

      Jonathan Paton

    3. Re:still relevant? by hydroponx · · Score: 1

      From Perl.org: Perl is a general-purpose programming language originally developed for text manipulation It evolved into a system admin language as time went on and modules were created/added....

    4. Re:still relevant? by bsDaemon · · Score: 1

      Much of system administration scripting is manipulating text. Nearly every log or config file is in pure text, and commands take text in and spit text out, which is why Perl is so great for system admins. The general purposeness of it helps make the program flow easier to deal with for me. If I'm throwing something together on the command line, then awk, sed, cut, etc are fine. If its something I intend to use over and over again, then Perl helps me write a more permanent solution, which, at least to me, will be easier to modify later on as well.

    5. Re:still relevant? by jonadab · · Score: 1

      > it seems like perl has slowly moved from an ubiquitous scripting
      > language to a fringe research project over the last few years

      Perl is not an ubiquitous scripting language.

      Perl is *the* ubiquitous scripting language. That hasn't really changed. There are a number of other scripting languages, some of them newer than Perl and being used more and more (notably, Ruby), and some of them older than Perl and being used less and less (notably sh), but what hasn't changed in the last fifteen years is that Perl is about as popular as the three next-most-popular ones combined. (I'm assuming here that Java and VB and C are not counted as scripting languages.)

      As far as "fringe research project", there are certainly a number of fringe research projects associated with Perl, but the same could be said of any other major programming language.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    6. Re:still relevant? by ThePhilips · · Score: 1

      do perl afficionados think that this new version will enjoy the success that its predecessors have had?

      Why should I care?

      I use Perl5 because it is perfect fit for what it is. If Perl6 would catch might attention, I might consider trying it too.

      Perl isn't about gathering design awards or topping charts. It's a robust tool for an array of *NIX related tasks. And not only.

      --
      All hope abandon ye who enter here.
    7. Re:still relevant? by Anonymous Coward · · Score: 0

      The primary audience for new Perl, in my opinion, is sysadmins with no background in programming or computer science who need a language they've heard of to implement solutions to problems that need to be fixed before the expert software developers have a chance to do it the right way.

      FTFY

  6. No, Dont Bother by omb · · Score: 2, Insightful

    Or hold your breath either

    Facile discussion of languages on /. is getting so old.

    1. Re:No, Dont Bother by aaptel · · Score: 0, Redundant

      You must be new here.

    2. Re:No, Dont Bother by Anonymous Coward · · Score: 0

      How can he be new if he knows it's old?

  7. If I had mod points... by turing_m · · Score: 0, Offtopic

    I'm still chuckling... nice.

    --
    If I have seen further it is by stealing the Intellectual Property of giants.
  8. perl 5 versus ruby versus perl 6 by bcrowell · · Score: 4, Interesting

    I do most of my coding in perl 5. Perl 5's implementation is rock-solid, and CPAN has an absolutely fantastic selection of useful modules for perl 5.

    If I was going to change to something other than perl 5, I would need some motivation. The clearest motivation I can see is that OOP in perl 5 is ugly and bolted on.

    With that motivation, I have dabbled in ruby enough to write one nontrivial app. The thing is, perl 5 still beats the heck out of ruby in terms of implementation and libraries. As an example of this, in my ruby app I wanted to use some regex features that were not available in ruby 1.8, so I ended up using ruby 1.9. But ruby 1.9, and its regex engine, are relatively raw and buggy, and I ended up having serious problems that I had to work around. (Yes, I submitted a bug report. No, it hasn't been fixed yet.)

    AFAICT, the main advantage of perl 6 over perl 5 is the same as ruby's main advantage over perl 5: OOP is implemented in a nicer way. The thing is, the disadvantages are even more magnified, because it's so raw and incomplete.

    My current reaction to the situation is to plan on continuing to code in perl 5 until, say, 2015, and then check back to see how much ruby and perl 6 have improved by then.

    1. Re:perl 5 versus ruby versus perl 6 by ultrabot · · Score: 1

      The clearest motivation I can see is that OOP in perl 5 is ugly and bolted on. With that motivation, I have dabbled in ruby enough to write one nontrivial app. The thing is, perl 5 still beats the heck out of ruby in terms of implementation and libraries.

      Trying out Python never occurred to you?

      --
      Save your wrists today - switch to Dvorak
    2. Re:perl 5 versus ruby versus perl 6 by Anonymous Coward · · Score: 2, Insightful

      Why would anyone want to use a glorified VB clone? I am sick and tired of seeing 'rock-star' Python and Ruby programmers trying to shove the new shiny toy in everyone's face. People have been using Perl for 20+ years, and they'll still be using it for 20+ years after Ruby and Python are a distant memory.

    3. Re:perl 5 versus ruby versus perl 6 by bcrowell · · Score: 1

      Trying out Python never occurred to you?

      I like python OK. I've used it as a teaching language. I haven't written much nontrivial code of my own in python. The impression I get is that since it's younger than perl, its implementation isn't quite as solid, and its libraries aren't quite as complete. As a language matures, the rate at which old code breaks decreases; I think perl is futher along than python in that regard. For some of the applications I'm interested in, like CGI apps, perl seems to have better libraries and documentation, since it's been in use for those applications for a longer time.

    4. Re:perl 5 versus ruby versus perl 6 by ojustgiveitup · · Score: 1

      Hmmm, I'm not sure in what ways Python could be considered in any way similar to VB, so I can't respond to that, but I thought someone should point out the irony of a Perl programmer being afraid of new tools. You sound just like the who were afraid of "scripting languages" back when Perl was an infant.

    5. Re:perl 5 versus ruby versus perl 6 by ojustgiveitup · · Score: 1

      It might just be because I'm not a very experienced Perl programmer, but I find the libraries in the ruby community to be easier to find, easier to use, and of generally higher quality. Could you point me to some examples of libraries that you use in Perl but could not find in Ruby?

    6. Re:perl 5 versus ruby versus perl 6 by ultrabot · · Score: 1

      Why would anyone want to use a glorified VB clone? I am sick and tired of seeing 'rock-star' Python and Ruby programmers trying to shove the new shiny toy in everyone's face. People have been using Perl for 20+ years, and they'll still be using it for 20+ years after Ruby and Python are a distant memory.

      The GP mentioned trying Ruby (and as such is not afraid of shiny toys) and disliking it because of bad implementation. In that light, Python would have been a great match.

      Please don't drag down Python in the "rockstar programmer" mire, it's a time-honed language that is being used for serious (non-web 2.0) stuff all the time. We all got beards, even.

      --
      Save your wrists today - switch to Dvorak
    7. Re:perl 5 versus ruby versus perl 6 by slimjim8094 · · Score: 4, Insightful

      How old do you think Python is? Look it up ... ... ...
      It's 18 years old. In fact, it's only 4 years younger than Python.

      I suppose you think Google, CERN, and NASA are stupid to be "using a glorified VB clone"?

      Maybe it is you that is wrong.

      --
      I have developed a truly marvelous proof of this comment, which this signature is too narrow to contain.
    8. Re:perl 5 versus ruby versus perl 6 by wayland · · Score: 2, Interesting

      To me, the things that keeps me coming back to Perl 6 is that it will have built-in grammars.  That may just be because of the kind of apps I try to write, though. 

    9. Re:perl 5 versus ruby versus perl 6 by Lazy+Jones · · Score: 1

      If I was going to change to something other than perl 5, I would need some motivation. The clearest motivation I can see is that OOP in perl 5 is ugly and bolted on.

      How about multithreading then? It's not only ugly and bolted on, it incurs so much overhead that it's basically useless wherever performance matters at all. I use Gearman now (rationale: might as well take something with the ability to use multiple systems / load balance / redundancy if you are taking such a performance hit), but it would be so much better if we could just have acceptable multithreading like a bunch of other languages (Java family incl. Scala, C/C++ if you are a masochist etc.).

      --
      "I love my job, but I hate talking to people like you" (Freddie Mercury)
    10. Re:perl 5 versus ruby versus perl 6 by abulafia · · Score: 2, Funny

      How old do you think Python is? Look it up ... ... ... It's 18 years old. In fact, it's only 4 years younger than Python.

      I take it then that it is some sort of 4-dimensional Oroboros?

      --
      I forget what 8 was for.
    11. Re:perl 5 versus ruby versus perl 6 by plasticsquirrel · · Score: 5, Funny

      Why would anyone want to use a glorified VB clone? I am sick and tired of seeing 'rock-star' Python and Ruby programmers trying to shove the new shiny toy in everyone's face. People have been using Perl for 20+ years, and they'll still be using it for 20+ years after Ruby and Python are a distant memory.

      Why would anyone want to use a glorified Unix Shell? I am sick and tired of seeing 'rock-star' Perl programmers trying to shove the new shiny toy in everyone's face. People have been using Lisp for 50+ years, and they'll still be using it for 50+ years after Perl is a distant memory.

      Now get off my lawn.

      --
      Systemd: the PulseAudio of init systems
    12. Re:perl 5 versus ruby versus perl 6 by Anonymous Coward · · Score: 1, Interesting

      Uhm, go to http://search.cpan.org/ and find anything you want. With a demonstration in the synopsis, and everything is installable with a robust command line tool that (sometimes is too) verbosely states any problems. It also has built-in error reporting on test failures, so you can interact with module authors very easily.

      I can't respond to Ruby in any way that isn't flamebait. I really, really hate gems -- when it works, it works great. When it fails, I can never figure it out. I will leave it as that.

      As far of higher quality, that could be it. Perl has had a long history, and with an open door philosophy a lot of really terrible code ends up on the CPAN. However, if you take a quick look at some of the Perl efforts to describe the high quality modules (Enlightened Perl Organization's Task::Kensho) it's all hand picked and vetted by hardcore perl hackers.

      Here's some things in Perl that I'm genuinely surprised more people haven't jumped on:

      Moose (Class::MOP) giving you an entire meta-object protocol to get closer to functional programming
      DBIx::Class - a relational ORM that truly understands SQL, with some really amazing features.

    13. Re:perl 5 versus ruby versus perl 6 by edelbrp · · Score: 1

      I've been a long time Perl 5 developer, and have been doing a lot of Ruby since RoR was in beta. I haven't had a lot of issues with Ruby, to be honest. Most of the important CPAN modules have been ported to RubyGems and most of the serious Ruby bugs have been fixed.

      Some things which make Ruby great: It's a very nice OO language. Rails is basically the standard web framework used (Perl 5 has many to choose from, so inheriting a Perl web project can be a pita).

      Some things which make Ruby not so great: It's sooo slow to start and requires mod_rails/fastCGI/Mongrel or some other special environment to be fast enough for production web-apps. The community (sorry) has a lot of n00bs that make it difficult to find truly talented programmers.

      BTW- I think it's a little cheap to compare Ruby with Perl 6. Ruby reached 1.0 in 1996, and Perl 6 hasn't reached production yet.

    14. Re:perl 5 versus ruby versus perl 6 by ojustgiveitup · · Score: 1

      Didn't mean to suggest a comparison with Perl 6, but rather Perl 5.

      Don't see any difference in the requirement of mod_rails/etc. versus mod_perl/mod_php/fcgi for those languages. Impossible to argue about start-up time and performance in general, although I think Ruby is working more on that problem than nearly anyone right now (1.9/JRuby/Rubinious/etc.)

      The community doesn't seem hugely different than others I have been part of (not many), but of course I'm somewhat of a n00b myself :) It is true that there are lots of "Rails programmers" out there who don't really know Ruby. You don't see that much elsewhere it doesn't seem.

    15. Re:perl 5 versus ruby versus perl 6 by FlyingBishop · · Score: 1

      The thing that makes me suspicious about Python is that the people who are trumpeting it's greatness are by and large the people who were so keen on Lisp. To some extent perhaps they're just learning the error of their ways, but still. It doesn't look right.

    16. Re:perl 5 versus ruby versus perl 6 by wayland · · Score: 1

      Wasn't it Paul Graham that said that Java was good because it took a lot of C programmers, and carried them part way to LISP?  You can say the same about Perl, but even more so :). 

    17. Re:perl 5 versus ruby versus perl 6 by bcrowell · · Score: 1

      Could you point me to some examples of libraries that you use in Perl but could not find in Ruby?

      Interesting question. Okay, here's the list of all the CPAN modules that I routinely install on a system I'm going to use: CDDB_get, Term::ReadLine, Term::ReadLine::Gnu, Term::ANSIColor, Term::ReadKey, Curses, Mail::Sort, Net::DNS, Net::DNS::Resolver, Mail::Address, Mail::RFC822::Address, Mail::Sendmail, Digest::SHA1, Data::Dumper, XML::Parser, XML::Simple, Data::Dumper, Time::HiRes, RTF::Tokenizer, RTF::TEXT::Converter, Clone, Term::ReadKey, Date::Calc, Digest::SHA1, Digest::Whirlpool, Tk

      A quick, casual sampling in RAA and RubyForge shows that indeed, a lot of these are also available in ruby. It's a little hard to tell, however, how to really compare. Some problems with comparisons: (1) I think some modules, e.g., Clone, are probably not necessary in Ruby; (2) it would be time-consuming to go through and find out what functionality was equivalent to what in all these cases; (3) there's no quick and easy way to compare quality; and (4) if I'm writing software for other people to use on linux, it makes it much more convenient for them if it's widely packaged by various linux distributions. Just as a random example, at one time I wrote a perl app that depended on two CPAN modules called Audio::Data and Audio::Play. Turned out that was a big mistake. The quality of the code was very poor, the author stopped supporting them, and there were portability issues. So I could have pointed to those two modules and said, "Look, perl supports this!," but actually it would have been misleading.

    18. Re:perl 5 versus ruby versus perl 6 by Anonymous Coward · · Score: 1, Interesting

      There is a huge difference between languages like Lisp and Haskell, and languages like Perl, Python, and Ruby. The former are languages that allow for high order functions that manipulate the language, and allow full abstraction without arbitrary limits.

      For example, when object-oriented programming became a new and exciting thing, Lisp programmers immediately started making their own object system. To do this, they did not need to change the language in any way, they could simply create it within the language because Lisp has such powerful abstraction and metaprogramming abilities.

      Today Lisp is one of the two languages that the creator of OO programming (Alan Kay) will acknowledge as fully embodying proper OO programming. He also says that it's the single most important programming language ever created.

      Compare that to languages like C++, Perl, Python, etc. who no one with any respectability will even acknowledge as having a well-designed object system. Their object systems are incomplete, hacky, and ridiculous. However, in Lisp, building such things does not even involve changing even a little bit of the core language, and the syntax fits perfectly with the rest of the language.

    19. Re:perl 5 versus ruby versus perl 6 by mypalmike · · Score: 4, Funny

      (problem (((car 'some-apostrophe-shit) lisp (with #letrec foo * (lambda x) (x unmaintainable +))) parentheses (nobody-can-read-this-crap !) (worse-than (cons perl))) (interesting-cs-teaching-language cdr (though))))))))))))))))

      --
      There are 0x40000000 types of people: those who understand 32-bit IEEE 754 floating point, and those who don't.
    20. Re:perl 5 versus ruby versus perl 6 by ojustgiveitup · · Score: 1

      Yeah I suppose it's tough to compare for all the reasons you mention (and probably more). By the way, while most popular libraries are still available on RubyForge, the bulk of newer and smaller libraries are on GitHub these days. The availability of distribution-packaged libraries is definitely a valid concern, but IMHO, rubygems are easier to use than CPAN and could or should be more widely distributed by default in the future. Food for thought!

    21. Re:perl 5 versus ruby versus perl 6 by bcrowell · · Score: 1

      rubygems are easier to use than CPAN

      CPAN's user interface is definitely very 1994 :-) Perl programmers seem to accept it, but it seems pretty silly to me the way it makes you hit enter 37 times to accept all the defaults.

    22. Re:perl 5 versus ruby versus perl 6 by Anonymous Coward · · Score: 0

      You've never bothered to learn Lisp, so why post nonsense like this that isn't even formatted? It's like posting C or Perl without any newlines or indentation.

      People who have actually learned Lisp or Scheme know that it isn't necessary to count parentheses or focus on them. In fact, modern editors use a darker color for the parentheses because they're just the outer shell. The syntax is so dead simple that anyone can learn it (even you), and before long it's easy to read. However, people who come from C and Perl backgrounds think the parens are terribly important, so they mindlessly count them and just focus on those. That isn't the point of Lisp, and good formatting makes this unnecessary.

      However, learning this requires actually making an intellectual investment in something that is different. Less intelligent people are unlikely to do such a thing. This is why Lisps and other functional languages are not used by people such as you.

    23. Re:perl 5 versus ruby versus perl 6 by Reality+Master+101 · · Score: 1

      I've been working with Perl 5 as my primary development language for about 10 years, and while I love what Perl does well, what Perl doesn't do well (particularly objects and error handling) SUCKS.

      I've recently had the very surprising pleasure of doing a new project in PHP. Now, if you haven't used PHP lately, you would probably be moaning to some degree like I did, but you know what? PHP 5.3 has grown into a real language. Yes, there is still some library inconsistency and cruft, but it has most of the features one expects from a modern language, and PHP compares very favorably with Perl in terms available libraries and functions.

      I'd never thought I'd see the day that I enjoyed PHP, but it's really grown into a nice language. No, it still doesn't have the syntactical shortcuts that Perl has (e.g., regular expressions as fundamental operators), but I don't care. It's been such a pleasure having real objects and relatively real exceptions that I'm actually starting to hate using Perl and its ancient crap.

      --
      Sometimes it's best to just let stupid people be stupid.
    24. Re:perl 5 versus ruby versus perl 6 by chromatic · · Score: 1

      That was Guy Steele, talking about C++ programmers.

    25. Re:perl 5 versus ruby versus perl 6 by FreakyGreenLeaky · · Score: 1

      Just ignore them, use whatever tool you think is best and get the job done. I'm sure Python/ruby/* are fantastic tools, but Perl works for me on so many levels.

    26. Re:perl 5 versus ruby versus perl 6 by pmontra · · Score: 1

      No because of its semantic indentation. It's a religious issue and I'm on the other side, the Right One :-)

    27. Re:perl 5 versus ruby versus perl 6 by Junta · · Score: 1

      I will say he was overly dismissive of python and ruby, but there is a kernel of truth there. Beware of any language that is a current fad. No matter how good it is, it will be advocated and tried to be used even in places where it doesn't make sense. "Ruby on Rails" did that to ruby for a time (not sure about now) and Python is still very much in the fad stage where a recommendation should be noted, but taken with a grain of salt. I'm not saying this doesn't happen for languages that aren't "hip" (for example perl), but it is a bit less prevalent.

      Personally, I think people get too worked up over other people's choice in programming language. At the end of the day, most are equally capable given the right knowledge and resources.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    28. Re:perl 5 versus ruby versus perl 6 by ojustgiveitup · · Score: 1

      +1000 on your last paragraph.

      In response to your first point - my thing is, how do you ever know when something stops being a fad? Was using 'C' a fad right when UNIX came out? Maybe it was, but it definitely isn't now, so when did it change. Was Java a fad when it first came out? Is it now? For those of who say yes and yes, what makes it so - a *huge* number of people use it to great success. Same goes for Ruby and Python.

    29. Re:perl 5 versus ruby versus perl 6 by Anonymous Coward · · Score: 0

      It's been such a pleasure having real objects

      Define "real objects" (in the context of object-oriented programming).

      (Hint: if you say anything other than "collections of bits in a computer" you're a deluded fool, there's nothing that makes PHP or Python's objects any more "real" than Perl's.)

    30. Re:perl 5 versus ruby versus perl 6 by Reality+Master+101 · · Score: 1

      Define "real objects" (in the context of object-oriented programming). (Hint: if you say anything other than "collections of bits in a computer" you're a deluded fool, there's nothing that makes PHP or Python's objects any more "real" than Perl's.)

      A "real object" has a language syntax that is comprehensible, maintainable, and well-defined. Not to mention a syntax that I can use on a casual, daily basis without having to copy some other working code and/or consulting the manual.

      (Hint: You're a dumb-ass. The important aspect of HLLs are how the abstractions make it easier to be productive. We all (i.e., knowledgeable people) understand that high-level languages are abstractions on low-level data manipulations over time. That you feel the need to point this out just tells me you fell off the turnip truck very recently. Congratulations. But you still don't get to eat at the adult table.)

      --
      Sometimes it's best to just let stupid people be stupid.
    31. Re:perl 5 versus ruby versus perl 6 by ajs · · Score: 1

      The impression I get is that since it's younger than perl, its implementation isn't quite as solid, and its libraries aren't quite as complete. As a language matures, the rate at which old code breaks decreases; I think perl is futher along than python in that regard.

      It is, but that's not a function of age, it's a function of adoption. Because Python was around for longer than Perl was before its adoption took off, the fact that they're of comparable age isn't as interesting as their timelines.

      That said, Python has its own problems. It's been built on a foundation of axiomatic correctness in a realm that has no absolutes, and thus often finds itself having to compromise in difficult ways (ternary operator that isn't quite a postfix conditional even though those are evil, partial lambdas, and many other odd warts are a result of this struggle to maintain the illusion that there are correct and incorrect choices in language design).

      I enjoy Python and work in it often, but I'll be happy when I can switch fully over to Perl 6 because I'll be able to return to a world where best practices are hammered out over time with the deliberation of thousands of programmers, not enshrined up-front by someone who's going with a feeling.

    32. Re:perl 5 versus ruby versus perl 6 by badkarmadayaccount · · Score: 1

      There is not one single technical reason to use C. It exists by virtue of inertia and ubiquitousness.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    33. Re:perl 5 versus ruby versus perl 6 by badkarmadayaccount · · Score: 1

      Sad thing is, there is Python to lisp compiler. It's called pyjs.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    34. Re:perl 5 versus ruby versus perl 6 by badkarmadayaccount · · Score: 1

      Funny, the above sounds quite right about JS.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    35. Re:perl 5 versus ruby versus perl 6 by badkarmadayaccount · · Score: 1

      WTH? Is that using a buggy curses implementation or something? Well, at least it is somewhat... fitting of Perl. In an ironic way.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    36. Re:perl 5 versus ruby versus perl 6 by Anonymous Coward · · Score: 0

      A "real object" has a language syntax that is comprehensible, maintainable, and well-defined.

      Like Perl's, you mean?

      Not to mention a syntax that I can use on a casual, daily basis without having to copy some other working code and/or consulting the manual.

      Oh, I see, it's all defined by your ability (or lack thereof).

      (Hint: You're a dumb-ass. The important aspect of HLLs are how the abstractions make it easier to be productive. We all (i.e., knowledgeable people) understand that high-level languages are abstractions on low-level data manipulations over time. That you feel the need to point this out just tells me you fell off the turnip truck very recently. Congratulations. But you still don't get to eat at the adult table.)

      (Hint: You're a dumb-ass. You missed the point, epicly. What is it that makes PHP's objects more "real" than Perl's, other than your religion?)

    37. Re:perl 5 versus ruby versus perl 6 by ojustgiveitup · · Score: 1

      What should all those lines of C out there be rewritten in? What should they have been written in to begin with?

    38. Re:perl 5 versus ruby versus perl 6 by badkarmadayaccount · · Score: 1

      Ada, Lisp, Strongtalk, strongly typed JS. Depending on application.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    39. Re:perl 5 versus ruby versus perl 6 by DocHoncho · · Score: 1

      That would be the inertia he spoke of

      --
      Celebrity worship is a poor substitute for Deity worship and costs more to boot.
    40. Re:perl 5 versus ruby versus perl 6 by ojustgiveitup · · Score: 1

      I wasn't referring to the difficulty of re-writing all the lines (the inertia factor). I'm genuinely curious what people who dislike C believe is now, or would have been then, a better language for the systems programming that C has been mainly used for.

    41. Re:perl 5 versus ruby versus perl 6 by ojustgiveitup · · Score: 1

      I don't know much about Ada or Strongtalk, but I don't think Lisp or JS would be suitable for systems programming. From the little I know about Ada, it sounds possible that it would have been a good choice. What about D?

    42. Re:perl 5 versus ruby versus perl 6 by badkarmadayaccount · · Score: 1

      Flew right outta my head. But it seems like it offers nothing the others don't. And I don't see a reason to not use a properly typed JS for systems. I mean, what's wrong with it? The event paradigm matches perfectly, you don't have to fiddle around with classes, and still get an object system, looks quite like C, all you need is a way to interface the actual hardware. That can be done by simply compiling Verilog RTL interface specs as a runtime environment. Interrupt.mask(false).Ethernet, anyone?

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    43. Re:perl 5 versus ruby versus perl 6 by ojustgiveitup · · Score: 1

      ha! i like it. you make it and i promise i'll get started re-writing the Linux kernel!

    44. Re:perl 5 versus ruby versus perl 6 by badkarmadayaccount · · Score: 1

      Actually the whole project is out there, only in pieces. I'm just stating what can be easily built. The tweaks to the JS engine, the only serious programming (I think) is something like a week of work, so I guess you better start porting already 0 the actual project is almost none of the work. ;P
      BTW, thanks for the compliment. But the brings up the issue, what is supposed to go in a kernel? We've moved the hardware specific stuff in the compiler/runtime. I propose a library/object based self modifing/JIT Synthesis style kernel, using compiler based protection, instead of the usual hardware augmented kind.

      --
      I know tobacco is bad for you, so I smoke weed with crack.
    45. Re:perl 5 versus ruby versus perl 6 by aevans · · Score: 0

      Funny, it was things like Moose (and it's billion relatives, all trying to implement OOP in Perl), and DBIx::Class (and it trillion relatives, all trying to implement DAO in Perl) that made me finally turn away. And it was CPAN, with it's infinity of broken modules each with their dependency on an infinity of experimental modules for which the required (conflicting) version no longer exists in CPAN that made me hate Perl.

    46. Re:perl 5 versus ruby versus perl 6 by Anonymous Coward · · Score: 0

      easier to find? CPAN is too difficult?

    47. Re:perl 5 versus ruby versus perl 6 by gknoy · · Score: 1

      Exactly.

      If you're coding Lisp in Emacs, it wull automagically indent your code to the Proper Place, and that makes the parentheses much MUCH easier to follow. I wish that other editors (UltraEdit, Notepad++, some IDEs) supported Lisp as well as Emacs does, even if it were only syntax highlighting and auto-indentation. I'm addicted to that, now. I even like it in other languages. (Even if I haven't figured out how to get Emacs to indent my Perl or Java code the way I'd like it to be, it at least is consistent.)

  9. Still not APL by RichMan · · Score: 0, Flamebait

    It looks like they are attempting to reinvent APL. (with the addition of regex operations).

    I can imagine a single line of code will now require 10 to 100 lines of comments to describe the iterations and references going on.

     

    1. Re:Still not APL by Anonymous Coward · · Score: 0

      That's because you assume that the people reading the code will be Perl-illiterate like you.

    2. Re:Still not APL by Anonymous Coward · · Score: 1, Interesting

      Actually, it's because he correctly assumes that it's easy for two different perl programmers to use different styles and subsets of the language. Perl makes it easy to write code that's hard to understand unless you're the original author (a similar thing can happen with C++), and when that happens you'd better hope the documentation is ok.

  10. I first heard Perl 6 when I was in high school by Anonymous Coward · · Score: 0

    I remember my classmates talked about Perl 6 and the Perl Virtual Machine when I was in High school. Now I'm graduating from college, and Perl 6 still hasn't been released.

    Back that time he used Perl while I sticked with Python. Funny how time slips away.

    1. Re:I first heard Perl 6 when I was in high school by chromatic · · Score: 3, Informative

      Perl 6 still hasn't been released.

      We've released a new version of Rakudo Perl 6 every month since December 2007. That's 24 months in a row.

    2. Re:I first heard Perl 6 when I was in high school by bigdaisy · · Score: 1

      We've released a new version of Rakudo Perl 6 every month since December 2007. That's 24 months in a row.

      Those were "development" releases. How many of those releases could anyone confidently use in place of Perl 5 in a production environment?

    3. Re:I first heard Perl 6 when I was in high school by chromatic · · Score: 1

      How many of those releases could anyone confidently use in place of Perl 5 in a production environment?

      You changed your argument (from "You haven't released any software!" to "I don't think I would use the software you released!".) Even so, the amount of confidence anyone has in any particular Rakudo release depends on who that anyone is, what that anyone uses Perl 5 to accomplish, and what a production environment means to that anyone.

  11. Evil number by gmuslera · · Score: 1

    6 seems to be the number of the thing you want, is about to come, and takes forever to finally come, if ever. Is not a coincidence that the number of the devil is 666, should be an unlisted sin or punishment in hell that forever waiting for something that from the start was promised to come soon. IPV6 is another much wanted "imminent" upgrade that will take still a big while to come, and i bet that Duke Nukem Forever was planned to get out in the 6th iteration. I hope that PHP6 dont takes the same fate as Perl and comes when scheduled.

    Anyway, between waiting and getting a half-baked product, with problems that will avoid it being ever widely adopted, i prefer to wait till is really done.

  12. the "by xmas" curse by ysth · · Score: 1

    CERN recently invoked the curse too: http://press.web.cern.ch/press/PressReleases/Releases2009/PR18.09E.html.

  13. Perl6 Advent Calendar on PHP by heeen · · Score: 0, Offtopic

    Why couldn't they use a Perl blog framework like Movable Type instead of Wordpress...

    1. Re:Perl6 Advent Calendar on PHP by MathiasRav · · Score: 1

      Maybe because PHP is a web dev tool, and Perl is a sysadmin/text manipulation tool? I'm not one to vouch for either Movable Type or Wordpress, but even though Perl seems more efficient and faster than PHP, I'd rather use PHP for website frontends.

    2. Re:Perl6 Advent Calendar on PHP by Anonymous Coward · · Score: 0

      Maybe because PHP is a web dev tool, and Perl is a sysadmin/text manipulation tool?

      Perl is a general purpose programming language. PHP is a heap of shit.

      even though Perl seems more efficient and faster than PHP

      There are plenty of things more important than "fast" and "efficient", and PHP fails at all of them.

      I'd rather use PHP for website frontends.

      Why? Because of some magical "web dev tool" label? Because the PHP developers say it's better, so it must be true?

    3. Re:Perl6 Advent Calendar on PHP by Anonymous Coward · · Score: 0

      PHP is a heap of shit.

      Maybe you should have said "PHP is a Pile of Horse Poop"?
       
      ... I'll leave quietly.

  14. Other Advent Calendars... by sjstrutt · · Score: 0, Offtopic

    24 ways takes a general forus on web development while PHP Advent is supposed to be [1] more PHP focused.

    [1] Though that doesn't seem to *actually* be the case...

  15. It makes the easy stuff easy ... by parisjackson · · Score: 0

    and the wait for Perl 6 take forever

  16. Relevance vs Effectiveness by weston · · Score: 1

    the pascal/modula-2/oberon phenomenon

    Funny, that's what a lot of people who liked modula-2 and oberon have said about the recently released Go.

    do perl afficionados think that this new version will enjoy the success that its predecessors have had?

    Do you mean popularity or success?

    Popularity is related to its success, since a bigger community can provide a significant boost to a language, both in terms of library development and in terms of perceived viability as part of a commercial product.

    But widespread use isn't really the same thing. If it's an effective and pleasant tool for those who choose it, then it's successful.

    (And sometimes, a small, experienced, and smart community puts out better libraries and tools than a large one. Consider PHP.)

  17. Perl Advent calendars... by MSittig · · Score: 2, Informative

    A Perl Monks poster has collected the address of 5 different Perl(-related) advent calendars:

    http://www.perlmonks.org/?node_id=810472

    As he says, a "great tradition".

  18. Nock nock by Anonymous Coward · · Score: 0

    who's there?
    Perl 6

  19. What is Perl 6 anyway? by Godefricus · · Score: 1

    I still haven't figured it out yet, so let me take this chance.
    Can someone help me clarify: am I right about this?

    - Perl 6 is the successor to Perl 5, it will not exist as an implementation but as a specification. That specification is finished and definitive. It is owned by Larry Wall and small circle of his friends. They want everyone to implement interpreters for Perl 6;
    - An official test suite for Perl 6 exists and it is complete. Anything passing this test suite IS Perl 6. The test suite is stored with Pugs, an "early" attempt at a Perl 6-implementation that is no longer developed;
    - Perl 6 will not be interpreted directly by any one interpreter, like earlier versions of Perl, but it will be interpreted by a VM (Parrot) that 'plays' bytecode fed to it by several language-specific bytecode-compilers that act as plug-ins to Parrot. Parrot is owned by a bunch of friends of Larry Wall;
    - Several groups of people started implementing Perl 6. Pugs was one of the earliest. It is now unfinished and dead. Rakudo is the implementation-in-progress that gets the most attention now, because it is closest to being finished. It will be released for production in April 2006, which will mean "Perl 6.0 is out and it works". As with Pugs and any other bytecode-compiler for Perl 6 though, you will need Parrot to run it. Rakudo, Pugs et cetera are owned by their respective developers.

    Forgive me the long description of what I now think is Perl 6, but the various websites I try to find answers on aren't making it a lot more transparent.

    Could someone comment on this if I misunderstood something?

    And what about these views. Are people right who say:
    - Perl 6 is not finished by any means, but the people working on it don't seem to care as much, and instead go on to question the validity of the concept "finished".
    - Meanwhile, Perl 5, the ruling king of scripting languages has become fringe, and Perl 6 is largely viewed as a toy for philosophically-minded scholars.
    ?

    1. Re:What is Perl 6 anyway? by Godefricus · · Score: 1

      oops.. I meant 2010, not 2006.

    2. Re:What is Perl 6 anyway? by Anonymous Coward · · Score: 0

      "Perl 6 is the successor to Perl 5, it will not exist as an implementation but as a specification. That specification is finished and definitive. It is owned by Larry Wall and small circle of his friends. They want everyone to implement interpreters for Perl 6;"

      Incorrect. Perl 6 is a specification rather than a particular implementation (one of the major problems with Perl 5 is that the only spec is 'what the Perl 5 interpreter accepts', which is not particularly helpful if you want to produce another implementation, or a variety of language-aware tools), but the specification is currently unfinished. The spec is also very open - contributors are always welcome. There's discussion of the development of the spec on the perl6-language list and in the #perl6 IRC channel on Freenode. Commit bits for the SVN repo where the spec lives are easy to get hold of. In practice, most of the changes are made by a core group, but that's because they're the people who've made the effort to understand it and think about it, and they're often working on the results of discussion with various others. Larry Wall tends to get the final say, but there are good reasons for that (he's usually right, and he's the one who came up with the whole Perl vision in the first place).

      "An official test suite for Perl 6 exists and it is complete. Anything passing this test suite IS Perl 6. The test suite is stored with Pugs, an "early" attempt at a Perl 6-implementation that is no longer developed;"

      Like the spec, the test suite is incomplete, but otherwise that's essentially correct.

      "Perl 6 will not be interpreted directly by any one interpreter, like earlier versions of Perl, but it will be interpreted by a VM (Parrot) that 'plays' bytecode fed to it by several language-specific bytecode-compilers that act as plug-ins to Parrot. Parrot is owned by a bunch of friends of Larry Wall;"

      Partially correct. Rakudo Perl is a Parrot-based compiler to run Perl 6 on the Parrot VM. The other Perl 6 implementations do not use Parrot at all. Parrot was envisaged as part of the original plan for Perl 6, and it seems likely that Rakudo+Parrot will be the 'norm' at least at the start, but we're quite excited by the possibilities of running Perl 6 on the .NET DLR, or for the implementation which targets SMOP. Parrot's ownership is with the Perl Foundation, I believe.

      "Several groups of people started implementing Perl 6. Pugs was one of the earliest. It is now unfinished and dead. Rakudo is the implementation-in-progress that gets the most attention now, because it is closest to being finished. It will be released for production in April 2006, which will mean "Perl 6.0 is out and it works". As with Pugs and any other bytecode-compiler for Perl 6 though, you will need Parrot to run it. Rakudo, Pugs et cetera are owned by their respective developers."

      Pugs was invaluable in helping the Perl 6 spec to develop, as ideas were tried and refined in an environment that let code actually be written. It stalled and has faded into the background over the last few years, which has let Rakudo take centre stage. Rakudo is the most advanced implementation, and Rakudo *, scheduled for April 2010, will be a usable release people can use for a variety of tasks. It will not, however, be complete - there are parts of the Perl 6 spec that we know won't make it into *, and there are other parts of the spec which haven't been written yet - particularly gaping areas currently include the standard library, concurrency (except the implicit concurrency of hyperoperators) and foreign function calls.

      I hope that gives you a better idea of what's going on.

      "Perl 6 is not finished by any means, but the people working on it don't seem to care as much, and instead go on to question the validity of the concept "finished"."

      You say that in a disdainful manner, but there is no such thing as 'finished' for a programming language. Is C++ finished? It's out there, it's widely used, but C++0x is still under development and widel

    3. Re:What is Perl 6 anyway? by chromatic · · Score: 1

      Parrot's ownership is with the Perl Foundation, I believe.

      This is a minor nit in an otherwise accurate post. The Parrot Foundation governs Parrot.

    4. Re:What is Perl 6 anyway? by wayland · · Score: 1

      Mod Parent Up

    5. Re:What is Perl 6 anyway? by spinclad · · Score: 1

      mod parent up: informative and accurate (modulo Parrot Foundation owning Parrot).
      +1 to anonymous coward (Matthew Walton)'s reply.

  20. Rakudo Star not a production release by zmotula · · Score: 1

    Rakudo Star is not a production release. In the linked blog pmichaud says he would like to stay away from words like "finished" or "stable" and calls Rakudo Star a "useful" and "usable" release. The "Star" itself means literal *, or "whatever", to get away from commiting versioning or release engineering terms. The release will be simply something you can hack on without major inconveniences.

    1. Re:Rakudo Star not a production release by chromatic · · Score: 1

      Rakudo Star is not a production release.

      Why not?

      Whether it's useful in production depends on who you are, what you do, and what production means to you.

      If I had a couple of libraries ported from Perl 5 to Perl 6 (simplified greatly by new features of Perl 6, of course), I'd use Rakudo in the core of my business. I might do that as of the Rakudo Star release.

    2. Re:Rakudo Star not a production release by zmotula · · Score: 1

      Clearly we are not using the same definition of a "production" release. In my vocabulary, production release is a stable release that most businesses except maybe nuclear powerplants can rely on. A release that was thoroughly tested for data-loss bugs, will not break things with another update, has some bugfix schedule and so on. I know you find this definition overly restrictive, but you can't simply "squat" a word with a meaning different from the mainstream. (Or you will create more problems than you solve.) There are certainly people who will be able to use Rakudo Star in the core of their business, but I don't think that is what the release is mainly for.

    3. Re:Rakudo Star not a production release by chromatic · · Score: 1

      Clearly we are not using the same definition of a "production" release.

      Clearly, but that was the point of my post. I won't use PHP or C++ in production, despite the fact that many businesses do successfully.

      If you try to cram all possible meanings of all possible uses into a single word, you overload it past the point of meaning. Patrick's goal with Rakudo Star is to release something that many people will find useful and usable. Whether you want to deploy it in a production setting is entirely up to you; we refuse to make that decision for you.

  21. The opposite is true by e70838 · · Score: 2, Insightful

    Perl for people with no background in computer science ? Are you serious ?
    My experience is that people who do not like Perl are generally weak in computer science. Perl internal is more similar to lisp than to shell. For example, closures are very effective in Perl.
    All the elegance of Perl need a good level of computer science to be fully understood.
    The sysadmins I have met that had weak background in computer science hated Perl and were very proud of their shell hacks.

    For me, the smart sysadmins solves quickly and elegantly the problem with Perl before the IT departement finished writing the specification of a steam engine.

  22. Perl... by Anonymous Coward · · Score: 0

    Because I hate the ASCII characters 65 through 90 and 97 through 122.

  23. Perl is Elegant by tjwhaynes · · Score: 4, Interesting

    Perl is one of those languages that most people meet in passing because someone else has hacked up a script to get something out of some file. Which is sad, because understanding what makes Perl different from other languages and why it is often a better choice for wrangling data isn't going to be obvious in one lousy foreach search-and-replace hack. And most people exposed to perl scripts in this manner fall over on the difference between scalar and list context and never discover why perl expressions like $lookup{$term}++ will save them years of work, while making their analysis scripts go faster.

    I write Perl modules day in, day out to cope with processing DB2 internals in an attempt to model and improve them. Object-oriented Perl makes this easy, fast and effective. Closures (which I'm sure aren't understood by 90% of the Slashdot community) back this up being able to create anonymous subroutines with data attached which can be processed later. Perl is also effective for parallel task analysis - I have modules for jobserving many tasks across multiple machines and Perl threads make it easy to fire a task off while something else is done.

    Perl is an essential part of data analysis for any serious volume of unstructured data. However, I'm not unhappy that it is little understood. Perl makes in the impossible merely hard. If everyone knew how to leverage Perl, I wouldn't have so much fun.

    Cheers,
    Toby Haynes

    --
    Anything I post is strictly my own thoughts and doesn't necessarily have anything to do with the opinions of IBM.
    1. Re:Perl is Elegant by Anonymous Coward · · Score: 0

      > perl expressions like $lookup{$term}++

      Now where do I start to RTFM?

  24. Not yet by Anonymous Coward · · Score: 0

    call me when done andreshidalgofondado@hotmail.com

  25. Non-Obligatory plug by sonamchauhan · · Score: 2, Informative

    To test out Perl 6 in an IDE environment, try Padre.
    http://padre.perlide.org/download.html

    NOTE 1: Install the 'Padre Standalone Plus Six' package, not the 'Padre Standalone' package)

    NOTE 2: If you install it on windows, ensure you have a few hundred MB to spare on c:\ -- the drive targeting for the Install MSI does not work properly yet.

  26. TRANSLATION by rpresser · · Score: 0, Flamebait

    "I, Toby Haynes, am a genius. You are not. Go away."

    So -- Perl 6, the language for stuck-up assholes.

  27. Partidge in a Parrot tree by aevans · · Score: 0

    The most obvious pun. What's the state of the onion like these days Larry?