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
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Why should I use it?" (Score:1)
Off the top of my head:
Devil's Advocate (Score:2)
(Attempting to channel a recalcitrant, skeptical PHP programmer....)
That's fine, but why should I care? I'm never going to use a Sequent, port my application to AIX 4 or DYNIX. It's nice that sysadmins can use Perl, but if I don't care about writing sysadmin scripts, what's the point?
Re:Devil's Advocate (Score:1)
Responding to the recalcitrant, sceptical PHP programmer rather than ziggy :-)
None.
Let me be clear. I'm not trying to say "you should drop PHP and use Perl". I'm saying "here are some reasons you should consider learning Perl as well".
If none of them apply, then don't learn Perl. Does
Re:Devil's Advocate (Score:2)
Your defending the argument with still more platitudes. Specifically, you're making a generalized argument that PHP programmers should learn more languages, but you're not saying anything specific about why PHP programmers should learn Perl. (
Re:Devil's Advocate (Score:1)
(still responding to the recalcitrant, sceptical PHP programmer...)
I thought the "targeting the other primary language used for web development" was fairly specific :-)
You say that as if it would be a bad thing!
Outside of front-end web development I've never seen PHP mentioned in a job advert. I've never been involved with, or known anybody involved with, writing back end code in PHP. Ruby, Perl, Python, Java and half a dozen others yes. PHP never.
Now I'm not saying that it's impossible to write back end code in PHP. Just that you're very unlikely to ever get work doing it. Go look at the job adverts for banks. Perl (and Python) pops up all of the time. PHP doesn't.
CPAN - because it will save you a stupid amount of time writing code that somebody else has already written. Existing client infrastructure - because there are a lot of existing clients out there with large chunks of Perl that they don't want to throw away.
Outside that nothing that is going to give you a massive increase in productivity. Lots of little things that will give you little advantages (like anonymous subroutines and other HOP/Lisp-ish things), but nothing earth shattering.
I don't think the reasoning is shallow (but I would say that :-). It's just not the sort of argument that says "You should drop PHP now and learn Perl. You'll be a lot better off".
You won't be better off if you drop PHP and learn Perl.
Don't do that.
You will be better off if you learn Perl (or some other language) as well. Perl is used in lots of places that PHP isn't. You will have more job opportunities in different domains. If this doesn't interest you don't learn Perl, or indeed any other language.
Reply to This
Parent