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
In the near future, the probability is close to zero. In the distant
future, I'll be dead, and posterity can do whatever they like... :-) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Learning good (Score:3, Interesting)
Given the market for jobs right now, and given that learning is a good thing, I'd say learn the new language(s). (Of course, this is assuming that you enjoy your work environment right now.) Neither Java nor C# are bad languages (as opposed to something like Visual Basic), and learning them may not only increase your ability to get jobs in the future but also your ability to think in and about Perl in different ways.
Additionally, you never know when Perl will come in useful for a project: I write Java in my day job, but I also created a nifty system in Perl to generate EJB code. Folks at work aren't prejudiced against Perl -- they just want to get things done.
Reply to This