As I struggle with ASP.NET, these words comfort me...

ASP is good for these reasons:

• It operates well on all Windows web servers since 1996. (And there's a surprising number of old servers out there still churning pages.) The last version of the ASP script engine (v3.0) was released coincidentally with Windows Server 2000 (IIS 5.0) and remains fundamentally unchanged since that time.
• It's well documented with many forums, books, and web sites dedicated to the purpose.
• There are many free script resources and tutorials available.
• Experts abound.
• It's capable of interfacing with old and new objects, components, services, etc. and continues to provide powerful server-side processing.
• Commercially available WYSIWYG editors like Macromedia's Dreamweaver are equipped with ASP script libraries and extensions.
• It's learning curve isn't intimidating. It's logic is still very approachable to newcomers and I'd argue still serves as a great introduction to server-side programming.
• Its successor (ASP.NET) is maturing and gaining popularity at break-neck pace.
• And best of all, and the reason I write this article, is that I am able to look at the ASP environment in its entirety -- from its beginning to its end -- all its history -- and make this list of things I do and do not like about it. There's no stress in wondering if the next version will fix the things I don't like; or if my current code will break on the next version web server. Instead there's a rather comfortable feeling knowing that it is what it is and always will be.

Read "ASP: The Beauty of a Dead Language"