I've considered making a similar proposal at my current outfit, and I would but for one thing: vast quantities of already-working ASP/VBScript code, and a team of developers who are Windows-heads, most of whom have never seen a line of Perl in their lives. They're all talented people, but this project is already too big and too critical for everybody to take time off and learn a new language.
My main frustration at the moment is that while Perl has things like Template, and Java has JSP/JSTL/custom tag libraries, ASP (sans .NET) has bupkes. Thus writing a large project in ASP that is maintainable and modular, is essentially impossible. I haven't tried PerlScript, but I don't see how it could fix this fundamental problem inherent in ASP as a platform.
Update: On second thought maybe I shouldn't be so pessimistic. The problem with ASP is that it gives you no modularity except through <!--#include ...-->. But with Perl you could simply create a set of modules that lives outside your web tree. In fact, you could even create one module per page, and have the ASP simply call the module for all the processing work, and constrain itself to simple output.
Update: On third thought, Apache::ASP seems very cool. I would try it.
OTOH I've been told that Apache does well on Windows, so you may want to look that way.
In reply to Re: Perl vs. ASP?
by Errto
in thread Perl vs. ASP?
by bkiahg
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |