Re: Why Perl

why perl?

foreach my $X (all_programming_languages()) {
 why $X
}
[download]

Honestly, I don't think you'll find many languages where you don't have people liking them, or disliking them. I personally enjoy doing my work in Perl, Ruby or zsh, and I dislike COBOL, BASIC and, somewhat, Java; but I'm sure you don't have to look far to find people with a completely different profile of preferences.

Just try it out for yourself. Unless you have a heavy number-crunching application, or something with very tight real-time requirements, Perl will be an option (though, for sure, not the only one).

--
Ronald Fischer <ynnor@mm.st>

Comment on Re: Why Perl Download Code

Replies are listed 'Best First'.
Re^2: Why Perl by Anonymous Monk on Feb 01, 2010 at 12:42 UTC
Unless you have a heavy number-crunching application, or something with very tight real-time requirements, Perl will be an option (though, for sure, not the only one). But also remember that premature optimization is a mistake. Go ahead and write that number cruncher in Perl, and profile it. Then rewrite problem areas with XS or inline C, if somebody hasn't already done that for you and uploaded it to CPAN, and profile it. Then rewrite problem areas with inline assembly! It sounds like a lot of work until you compare it with learning a new set of languages (yes, I'm assuming familiarity with C). On the other hand, that isn't a reason not to learn other languages or environments, especially as widely used as Python and MATLAB and R and such. But I prefer doing that when I have the presence of mind to enjoy it, not when I'm under a deadline. That's what brought me to Perl, after all.	[reply]

Replies are listed 'Best First'.

Re^2: Why Perl
by Anonymous Monk on Feb 01, 2010 at 12:42 UTC

Unless you have a heavy number-crunching application, or something with very tight real-time requirements, Perl will be an option (though, for sure, not the only one).

But also remember that premature optimization is a mistake. Go ahead and write that number cruncher in Perl, and profile it. Then rewrite problem areas with XS or inline C, if somebody hasn't already done that for you and uploaded it to CPAN, and profile it. Then rewrite problem areas with inline assembly!

It sounds like a lot of work until you compare it with learning a new set of languages (yes, I'm assuming familiarity with C). On the other hand, that isn't a reason not to learn other languages or environments, especially as widely used as Python and MATLAB and R and such. But I prefer doing that when I have the presence of mind to enjoy it, not when I'm under a deadline. That's what brought me to Perl, after all.

[reply]