I think that more than anything I'm tired of the debate. It's not so clear cut as "Linux vs. Windows" (hahaha).

Use Perl for whatever you want to use it for. Keep in mind that while it is very efficient, some other language may be more efficient at particular types of tasks. That's why Perl isn't written in Perl (but only perl can parse Perl *wink* ).

A well-rounded programmer will have a variety of toolbelts, each filled with a variety of useful tools. A well-rounded programmer will know when it's best to use his carpenter's toolbelt, and when it's better to use his mechanic's toolbelt. Some days he may even need his surgeon's toolbelt. They probably all have utility knives in them. But the MD's hammer has a rubber head, the machineists is ball-peen, and the builder's has a claw at the back side.

Back to the well-rounded programmer. He will know, "This is a job for C", or "Perl will do nicely here." He'll even know when it's very convenient to embed one in another. How does one get to this point? By gaining proficiency in a few prominant languages.

I'm not really one for the "flavor of the day" type languages. I tend to prefer to focus on the ones you see in widespread use. Sure, I may be missing the curved scalple with an eraser at the back end from my toolbelt by not delving into this week's new language. And eventualy a well-rounded programmer will have to get around to gaining some knowledge of a pretty broad base of languages. But stop trying to decide which one is best.

The best one is the one that you feel you can accomplish your task efficiently with. And I mean that with all the insight available to a wise programmer: consideration of not just getting the job done, but of maintainability, portability, and all the other things that may or may not be of concern. Learn Perl. Learn C/C++. Learn Java. Learn a couple others. Only then will you be equipped to decide when to put on which toolbelt. ...Nobody asked which was the best of The Village People. ;)