Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I think people are going to be slow to adopt Perl 6. I think most of us will keep using Perl 5 until we're forced to do otherwise because we're used to it.

    I don't pretend to think that just because I know Perl 5 I automatically will know most of Perl 6. I made that mistake already a long time ago with C & C++ - they have some basic similarities, but otherwise they're totally different languages. And guess what? I don't feel like learning yet another language.

    I've already got a handle on Ruby and

    • These days I don't tend to write Perl for work - mainly because I'm between engagements (and anyone willing to provide an endpoint will be happily received). So I do my Perl more or less exclusively for fun these days.

      I've been programming for a reasonable amount of time (around a decade or so) in various languages. One of my hobbies is learning new/different languages.

      I can program in Ruby and Python. Reasonably competently. Ditto for PHP, but I have to check the manual for the names of functions and met
        ---ict / Spoon
      • I don't see a need for the community to fragment too much. Eventually, Perl 5 will be as Perl 4 is now. Is that really too much of a bad thing?

        If Perl 5 will be as Perl 4 is -- meaning not used for anything except legacy code -- that means that a great many programmers will have moved on to other things that are not Perl. To expect that almost all the people who love Perl 5 will love Perl 6 is unreasonable, because they are too different from each other for that expectation to have any logical basis. So
        • Quite honestly, it didn't look to me as if Perl 6 was all that different from Perl 5. For sure, it adds quite a number of things, but Perl 6 is supposed to be able to read Perl 5 code (otherwise we lose CPAN, and then I'd definitely worry). Given the latter point, why not upgrade to Perl 6 once it's stable? You'll still be able to use your beloved Perl 5. Over time, you might see a few things that you like in Perl 6, and start using it (the language, no the interpreter) as well. I think that the transition will be very slow, and give us all plenty of time to adapt, whether we want to run or whether we don't care at all about the new stuff.

          I also don't think that the community will split. For sure, it will fragment but I very much doubt that it will fragment more than it already is. A problem to solve is just a problem to solve, and most of the time you don't need to refer to the actual language to help find a solution. I have no doubt that people will keep talking over the cracks, from one fragment to the next. For instance, when I think pipeline I think SAX, and the #openframe people laugh at me thinking something else. But it doesn't mean that we don't discuss our different and similar viewpoints, or try to help one another find a solution.

          I see no good reason to think that it'll be different when Perl 6 comes. I know I'll be an early adopter because I like a lot of what I've seen. I also know that I'll keep maintaining my Perl 5 modules for a long while (even though I might not add many features). I also know that I'll keep talking to Perl 5 people and won't laugh at their solutions, knowing that I'll be able to use them directly in Perl 6, and that the general idea underlying the code is what I'm really interested in anyway.


          -- Robin Berjon []