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.
  • Well, some of it, anyway. I'm aware of a few items I wrote pre-1999 or so that I think are still in use. And I'm about to have to evacuate all programs I've written between 2004 and the present from one machine to another, and it turns out there's a lot of other stuff on that machine I didn't know about -- and one item is several daemons I wrote between 1999 and 2001. I've changed jobs twice since then, including once being laid off! (But still managing to get other positions at the same company.)

    I re

    --
    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
  • There are ways to make the situation better or worse...

    Perl has a tendency to be write-only, so that could encourage lack of long-term use.

    It could be hard to install and maintain, so that would too...

    The thing I LIKE about CPAN is that it imposes maintenance level structure.

    That you use POD, that you have dist structures, etc etc.

    In my latest couple of projects, I'm doing something similar. Experimenting doing things in a dist-like fashion with a dozen distributions instead of a monolithic structure.

    With P
  • About half of the paid-for code I've written is now dead because the firms I worked for went bust. (e.g. Income £80M, expenditure £143M, result misery! and strangely zero prosecutions for trading while insolvent). The other half I infer is a project that got cancelled. Whereas the non-paid for code I've worked on is installed worldwide on more machines than the Linux kernel.