Re: How to answer "Perl is not secure" objections?

I know this probably isn't the sort of answer you're looking for, but maybe it would be best to ask Manager^3, in a way that makes him feel like you're complimenting his intelligence and tech savvy, that you've never heard of this and would greatly appreciate it if he could either point you to the resource he heard about Perl's "insecurity" from, or demonstrate with an example of his own.

The first step in debunking most myths is figuring out who told them first.

Comment on Re: How to answer "Perl is not secure" objections?

Replies are listed 'Best First'.
Re^2: How to answer "Perl is not secure" objections? by Argel (Prior) on Sep 06, 2007 at 19:26 UTC
I agree about discovering the source of the myth but I disagree with your approach. It would be much better to have his managers ask the question -- they will be much more familiar with Manager^3 and doing it that way avoids going over anyone's head.	[reply]
Re^2: How to answer "Perl is not secure" objections? by radiantmatrix (Parson) on Sep 06, 2007 at 21:57 UTC
See, I don't get to talk to Manager^3. I only get to hear the objections (filtered through others) and provide documentation to refute them. <–radiant.matrix–> Ramblings and references The Code that can be seen is not the true Code I haven't found a problem yet that can't be solved by a well-placed trebuchet	[reply]
Re^3: How to answer "Perl is not secure" objections? by CountZero (Bishop) on Sep 07, 2007 at 15:58 UTC
Aye that's where the ugly bits and pieces of company and office politics rear their monstrous heads. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James	[reply]