The strategy my team has used so far has been "use the right tool for the job".

We have a mail-blaster tool that can send millions of emails each day (Perl + Postfix on Linux).

We have a media-manager server that serves images and documents for 80+ moderate-traffic websites (mod_perl on Linux).

For the GUI stuff we use ASP (IIS/VBScript). Not my first choice, but the other developers only know VBScript and are unwilling to learn Perl. Rather than beating them over the head with Perl, we make sure that the Really Important Stuff is written on a stable, efficient platform (Perl + whatever on Linux) and let them happily hack away on whatever garbage they want.

Part of "Enterprise" software involves the ability for more than one developer in your "Enterprise" having the skill to hack on the code. Granted, VBScript is not the most efficient, elegant or powerful language, but I would rather see these guys make simple mistakes with a simple language than deal with the horrific mess they would make with Perl.

In the absence of testing, documentation, comments or even consistent indentation, I will opt for a *simple*, uncomplicated language that prevents the "developer" from doing anything too clever.

On the other hand, if I worked with folks who could comprehend the importance of commenting, testing, documentation and constistent coding style, I would opt for a more rich, robust language (like Perl).