:confused::confused::confused:

Why would you say that? It is used on many corporate websites. While linux has many strong languages (all of which can be configured on windows servers as well), many big companies run windows web servers. Usually windows webservers will have asp applications rather than php/python/ruby/perl applications.

On windows server it is used globally isn't?

Not at all - in places where Microsoft puts lot of money it's even more often used as PHP or simmilar languages.

Classic ASP or ASP.Net?

You won't see many new Classic ASP projects any more these days, but there are plenty of sites still using it. (and plenty of developer jobs for their upkeep)

Lots of legacy systems written in classic ASP out there. It is still in use but mainly to support existing products.

It does what it is advertised on the tin and does it correctly.

Why should it then be obsolete?

It does what it is advertised on the tin and does it correctly.

Why should it then be obsolete?

I suppose the first statement is a matter of personal interpretation (especially on the security front, as well as your opinion of VBScript), but I don't think there's any doubt that while Classic ASP might not be considered "totally obsolete" now, it's certainly going that way. I don't work with it too much (and never really have), but I remember recently reading that Microsoft essentially abandoned any major updates to it since .NET came out, and at this point there haven't been any substantial improvements to it for almost a decade. I think for modern web application programming, it's pretty fair to say that ColdFusion, Perl, WebObjects, etc. are obsolete; they all had their day in the sun to varying degrees but there aren't a lot of greenfield projects using them, which is likely the case with Classic ASP.

The number of programmers competent with it is surely going down as well, perhaps substantially, as has the number of jobs if a cursory search on some programming related job sites is any indication. I can't imagine too many people have come to it within the last 5 years; it's just not being taught anymore, and most of the people familiar with it from it's heyday have moved on to .NET.

As many classic ASP websites you see out there times it by about 20 for internal applications. There is no doubt that Microsoft encourages you to move to .NET for very good reasons. Hardly obsolete but if you mean classic ASP and are considering learning it, don't just go right to .NET.

Realistically speaking, Classic ASP should be generally considered to be obsolete.

.NET (aspx) is where it's at for Windows webservers at the moment. There's no reason to start a new project using classic ASP.

Though I've never really seen any *real* advantage of operating Windows+ASPX over Linux+PHP anyway. I do like .NET though, particularly for binary-based stuff as opposed to script-based stuff, it makes writing Windows apps tons easier.

It does what it is advertised on the tin and does it correctly.

Why should it then be obsolete?

So do most rotary phones, black and white TVs, VCRs and 9600 baud modems. How does "doing as advertised" correlate to obsolescence?