Times to avoid using the otherwise standardized language:

• When the runtime performance is critical, but the language in question can't support it.
• When the memory constraints are critical, but the language in question can't support it.
• When the security considerations are critical, but the language in question can't support it.
• When the use or re-use of an already-written library or application is critical, but the language in question can't support it.
• When sticking to the current workforce is critical, but the available workforce can't support it.

That said, it's usually high-capacity number crunching with no hardware assistance (raytracing, fluid dynamics, etc.) which fails the performance test for Perl (though see PDL). Everything else technical in nature is pretty well handled.

Any workforce issues is a matter of mindset: if you feel you need more discipline in your language, or less complexity in your language, I won't fault you, but I think you can get over it and leverage Perl's strengths.

--
[ e d @ h a l l e y . c c ]