Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Fear and Risk (Score:4, Interesting)

    by pudge (1) on 2002.07.24 13:41 (#11019) Homepage Journal
    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 waste of my time, unless it's something I want to do, and it isn't.

    You make an excellent point about it being another project, and how it is less threatening if it is another project. 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 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 tri
      • 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
    • I have no reason to change to Perl 6, with all its incredible uncertainty.

      This is a perfectly valid reason to not change over to perl 6. In fact, it's a damned good reason that's far too often overlooked in general. Change for the sake of change is often unwise, in perl and anything else. Yes, you need change to make progress, but swapping something brand new into production 'just because' is foolish.

      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 t