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.
  • Fear and Risk (Score:4, Interesting)

    When it comes down to it, people are afraid of change, plain and simple, for with change comes risk.

    I am not afraid of Perl 6, though I basically agree with your points. But I very much agree that I do not want to change, because with change comes risk. Why should I risk anything? Perl 5 is good. Perl 5 suits me well. I have no reason to change to Perl 6, with all its incredible uncertainty.

    In addition, it is not just risk, but time. Since I don't have any need for Perl 6, to switch to Perl 6 is a
    • I am told by the Perl 6 team that if I don't use Perl 6, and stick with Perl 5, that I am behind the times, that I am sticking with old stuff that isn't very good, that the future is Perl 6 and Perl 5 is a dead end. How is that not threatening?

      I stayed with perl 4, instead of moving to perl 5, for over 5 years. I "knew" that there were a large number of subtly incompatible changes with perl 5 and didn't want to track down the myriad subtle bugs that would start causing wierd problems.

      When I actually tried it out, it took half a day to fix the obvious problems (using @ in double quoted strings). Then the 30,000 line system was left running in parallel for 2 months - and no problems showed up that were actually the fault of perl 5. (The pointy-eyed boss saw lots of things to fix, but they were mostly all there in the original code too; and he found a number of items that were simply artifacts of running in parallel, in fact, sort of those artifacts he fould every week for the entire two months.)

      Perl 6, will certainly be a bigger change to update code, but not a huge amount bigger. (Doing a full rewrite to take proper use of new perl 6 idiom would be a big job - but that 30,000 line system still has lots of early perl 3 idiomtic code in it - it still works as it is even though I would never write it that way if I was coding it in perl 5. I did finally remove the eval around the "dbmopen" that had been there from the time that the code was running on some older versions of perl 3 that predated dbmopen - by then, dbmopen was deprecated!)

      I was quite impressed with Damian's "Perl 6 - The Sky Isn't Falling" talk when he gave it here in Toronto. There'll be a few things that require getting used to doing differently, but there will be enough things that are simply better to make it worthwhile.
      • Perl 6, will certainly be a bigger change to update code [than was Perl 5], but not a huge amount bigger.

        I disagree. I would have a ton of code to change to actually be using Perl 6. Thousands upon thousands of $ signs, if nothing else. Of course, there may be a Perl 5 compatibility mode of some sort, but if I am using Perl 5 anyway, what's the point?

        But again, with Perl 5, there was a reason to upgrade: to take advantage of the large number of modules, to fix longstanding bugs, to use OOP, etc. The
        • First off, I'm rather neutral about Perl6 maybe a shade positive.

          Now, I started using Perl back in 1996/1997 so I missed the transition from Perl4 to Perl5. However, I did have to deal with some code written in Perl4.

          My impression is that most people took several years to switch between the two and that most had switched (say a sigma or two of the population for the statistics folks out there) to Perl5 after 5 years. That's just a WAG on my part.

          I'm think that it will take almost 10 years for folks (a la