Classic ASP - is the market dead?

M

MisterBigglesworth

Expert Member
Joined
Aug 15, 2006
Messages
3,334
Reaction score
13
Location
/\\/¯¯¯\//\
Was chatting to some friends. Im more a classic ASP and PHP specialist...and will be moving to C#.NET this year. Anyways...some recon its not a dying speciality as many dont want to go the "convert to .NET" route and so stick to classic ASP, while others recon it will die out due to the advancement of the .NET framework etc?

What are your thoughts? :confused:
 
Ive stuck with classic asp as it does mostly what i want, if not, there's usually a component out there.

My number 1 reason for sticking with classic asp though is i like having FULL control over the script and output. Them .net one line out put a whole frekin form is "nice and all" but the moment one wants to customize it, then oig, what a nightmare
 
OMG I feel restricted when someone forces me to look at .NET, forget ASP. Writing boilerplate code is for the birds (ASP) and not having the ability to customize (.NET) is almost as bad.

Grails and/or Spring ftw.
 
stormwalkerza said:
Ive stuck with classic asp as it does mostly what i want, if not, there's usually a component out there.

My number 1 reason for sticking with classic asp though is i like having FULL control over the script and output. Them .net one line out put a whole frekin form is "nice and all" but the moment one wants to customize it, then oig, what a nightmare
Click to expand...

You obviously know nothing about .NET if you think you don't have full control.
 
There are more .net (C#) or Java jobs than there are Classic ASP. There will be a legacy systems written in vb6 or asp that need to be maintained.

I would suggest you get into that. I'm sure new projects will either go C# or Java and you don't want to be left behind.
 
CrazyFig said:
Was chatting to some friends. Im more a classic ASP and PHP specialist...and will be moving to C#.NET this year. Anyways...some recon its not a dying speciality as many dont want to go the "convert to .NET" route and so stick to classic ASP, while others recon it will die out due to the advancement of the .NET framework etc?

What are your thoughts? :confused:
Click to expand...

I'm in love with ASP.NET MVC 3 with the Razor view engine
 
Last edited:
I prefer Classic ASP since it doesn't need bloated resources or special libraries installed to function. I also don't need to rebuild/re-upload each time to check something. "Save file, F5"

But Classic ASP can't be compared to .NET since the two is fundamentally and significantly different to each other. There's nothing so complex you need .NET for that Classic ASP can't do quite simply. But having said that, PHP beats Classic ASP hands down IMO.

Learn and move to C#/PHP etc... don't stagnate. But don't write off the older technologies either. Simpler is sometimes much better... avoid VB6 though ;)
 
Its funny how all the classic ASP guys are looking for excuses not to go to VS .NET.

All I can say is you guys are missing out, classic ASP is a pain in the ass compared to VS .NET

If you want to do something using just html and scripting in VS .NET theres nothing stopping you, if you dont like a VS .NET component or control then write your own or overide the existing one.
 
stormwalkerza said:
Ive stuck with classic asp as it does mostly what i want, if not, there's usually a component out there.

My number 1 reason for sticking with classic asp though is i like having FULL control over the script and output. Them .net one line out put a whole frekin form is "nice and all" but the moment one wants to customize it, then oig, what a nightmare
Click to expand...

Have a look at ASP.net MVC, you get complete control over your output and it has the power of .Net
 
AcidRaZor said:
I prefer Classic ASP since it doesn't need bloated resources or special libraries installed to function. I also don't need to rebuild/re-upload each time to check something. "Save file, F5"
Click to expand...
ok, maybe bloated, but it is a huge library we are talking about (contains windows, web, mobile libraries etc). and all the windows servers we get have it anyway. Your last statement doesnt make sense though. You can code directly on the pages if you want and .net will compile on runtime - that is if its set as a web application. .net is way better than classic asp thats for sure.
 
Switched from Classic ASP to PHP. Not interested in .Net.
 
I have about +-7 years experience in vb6 and classic and I'm trying to unlearn everything from all them.
 
Sometime I have to make some ASP pages and I always use "plain, old" ASP 1.0 - I don't like complexity of 2.0 and wanna keep stuff as simple as possible. Our designer makes a template (with all styles dropped to css) and next I mix file with code sections. Deployment of such stuff is also more simple.
 
Vincent_Thorn said:
Sometime I have to make some ASP pages and I always use "plain, old" ASP 1.0 - I don't like complexity of 2.0 and wanna keep stuff as simple as possible. Our designer makes a template (with all styles dropped to css) and next I mix file with code sections. Deployment of such stuff is also more simple.
Click to expand...

WTF? I don't understand what the difference between 1.0 and 2.x is? I've always just did classic ASP... why force 1.0 when ALL servers even ****ing DESKTOPS with IIS support 2.x without installing 200+mb of .net libraries?
 
Classic ASP is a dinosaur and needs to die. Being an intepreted language, its much slower than .Net, and lacks significant features. It also doesnt lend itself well to good separation of concerns - too often I've seen presentation logic, database logic and business logic all in one file. Classic ASP projects tend to turn themselves into a huge mess, unless someone has an architect in charge who knows his stuff. Otherwise, its a chore to maintain.
 
If you still think Classic ASP is the best tool for the job then you clearly have no business being a programmer and clearly have no idea of object-oriented programming, design patterns, separation of concerns and all the other modern programming techniques that .NET allows you to practice. Try creating a presentation layer, business object layer and a database layer with Classic ASP and you'll have yourself twisted into knots. Try creating a web service with Classic ASP and you'll probably end up killing yourself.

Really guys, Classic ASP is a dinosaur that belongs in the nineties. .NET and C# is where it's at, and I can promise you if you know what you're doing with C# you will never be out of a job in South Africa. There is a MASSIVE shortage of skilled .NET developers in South Africa.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X