First of all, if it works for you, that is fine. They're tools, not religions - at least if you are in business.
Second, perl has its own problems. People complain about perl maintainability. It is easy to write a script that is hard for other people to understand in perl. Of course, if you follow good practice, you can write clear code in any language. If.
That said...
I haven't had much truck with ASP but one main problem with it - and PHP - is that they go for the "code embedded in web pages" approach. This is quick and easy, but it has serious problems. First of all, your designer has to wade through your programmer's incomprehensible geek gibberish, and your programmer has to scroll past your designer's hideous nests of TABLE tags. More importantly, this approach mixes in "application logic" with design.
For example, suppose you want to login a user. "User login" is a single concept. The code for it should be in one place. But because each ASP/PHP page can only display one web page, you have to break up your code. There's the code to display the login form and the code to display the result. These have to be split over two pages. That sucks.
You don't have to program like this (at least in PHP) but the design of the language encourages it. Beginning programmers mix code and display... then they end up with unmaintainable websites.
Perl is much more of a general purpose programming language than ASP or PHP, which are basically web solutions. As such, it supports a lot of different approaches: HTML::Template, CGI, HTML::Mason are all different ways of building web applications. And Perl has the power of CPAN, where there is a solution to pretty much any problem.
So basically, I don't know if ASP sucks, but I reckon Perl is better. It sounds like you are using it already... maybe you should upgrade.
dave hj~
In reply to Re: Why ASP is Awful?
by dash2
in thread Why ASP is Awful?
by NAstyed
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |