Re: Perl vs. ASP?

Have you described the alternate environment in which your Perl programs will live? Is it going to build on top of your existing infrastructure are are you requesting a bunch of UNIX boxes? The boss needs to know that one 'cos he isn't going to buy new hardware for the hell of it.

Have you listed the set of software that you would want to deploy? Are we talking Apache/mod_perl or are you sticking with IIS? If you are trying something new, can you assure him that the software can be administered?

Have you listed the positive points that your idea has over the alternate idea? Having done most of it is a plus point but is it prepared to the level where someone else can take over from you during the maintenance phase.

In short, you need a business case and a strategy.

Comment on Re: Perl vs. ASP?

Replies are listed 'Best First'.
Re^2: Perl vs. ASP? by bkiahg (Pilgrim) on Jun 10, 2004 at 13:01 UTC
It's essentially a rework of our current intranet. We'll be using the same box (2000, running IIS), so we won't have to order any new hardware.	[reply]
Re^3: Perl vs. ASP? by trialmonkey (Hermit) on Jun 11, 2004 at 01:49 UTC
If you must run on Windows consider a performance booster like PerlEx from ActiveState. The breadth and quality of the perl modules have certainly impressed my ASP oriented co-workers. It's easy to stand on the shoulders of those who have gone before you. I also like to do the sysadmin work in perl. I find it more suitable and enjoyable than vbscript.	[reply]