Re: Is there ever a time Perl is the wrong choice?

[Wysardry]

In general, any project where text doesn't make up the bulk of the processing or that involves low level access would likely benefit from being coded in something other than Perl.

Perl also tends not to scale very well in multi-threaded environments compared to other languages.

There are modules available to add functionality to the core language, but obviously this is less efficient than using a language with those functions built in.

I wouldn't want to attempt to code a raytracer in Perl, for example (or any math or graphic intensive program come to that).

Basically, Perl is a general purpose language with an emphasis on text processing, and if your project has a very specific task to perform, it will benefit from being coded in a language specifically designed for that task.

Adjustable spanners are okay for everyday use - such as bicycle maintenance - but you'd find it quicker and easier to use a quality socket set to strip down something like a performance car engine.

Choosing a programming language should be included as part of the design process, and whilst personal preference and experience level will be factors, suitability for the task should also have a high priority.

There's also an interesting (speed) comparison of 30 different computer languages at The Great Computer Language Shootout which you might find useful.

__________
"Every program has at least one bug and can be shortened by at least one instruction -- from which, by induction, one can deduce that every program can be reduced to one instruction which doesn't work." -- (Author Unknown)