Ok, So I moved this to meditations because it didn't fit in the "Seekers of Perl Wisdom Category.

On to your question - I have to say that I hate ASP! At my company, most people are familiar with ASP using VB script. Although people have started to get interested in Perl since I started, my current project is using ASP - and I'm writing it in PerlScript.

Once I got my head around the difference between PerlScript and Perl, I am faced with the problem that all my code looks ugly. People complain that Perl code looks like line-noise, well PerlScript is terrible - code mixed with raw html, mixed with here docs, mixed with god know what else, it makes it difficult to reuse code and very difficult to document. Also my editor doesn't quite know how to color-code the syntax!

However, there have been some benefits. In ASP with VBScript there is no built in sleep function. My colleague was going to install a component to do this, but I wrote him a nice bit of Perl that he can include in his scripts. Went something like this:

<script language=PerlScript>

sub wait_for {
   my $wait_for = shift;
   sleep $wait_for;
}

</script>
[download]

The flip side of this is that I can also use functions that my colleagues write in VBScript.

However, the whole way that ASP works seems backwards to me and makes maintaining and documenting code very difficult. I can't really speak about ASP with VBScript of JScript, but as far as PerlScript goes - it sucks. The only nice thing about ASP is the Session and Application Objects. But these can be implimented in straight Perl if you use the right modules.

$ perldoc perldoc