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.

Solutions Are Not Problems. Problems Are Problems. 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • I've been talking to a lot of people about this recently, and I usually ask the question "Why do you care if Perl survives?". Most people say the same thing that you say at the end of your post: "Our careers depend on it."

    I think that's a pretty poor reason to do anything, and certainly the worst of all the reasons to promote a programming language. If we're in a situation where we are merely trying to save jobs and keep Perlers employed, we're not doing the right thing.

    • Other people - and companies - might not care about my career, but I do. So I'd I thought career depended on perl then hell yes, "my career depends on it" is a damned good reason for *me* to care and to do something about it!

      • You should take anything your career depends on and make your career not depend on it. If Perl disappearing meant that your career was over, then you either aren't a valuable employee or need to diversify your skills. You should never have only a single thing that makes you employable.

        Knowledge of a particular programming language should be among the least of your skills. You should be valuable for your general knowledge of how things work, your experience in the problem domain, and your ability to solve problems with the tools you are given. If you don't have those skills, knowing Perl isn't very useful over the span of a career.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.