Is Classic ASP a lot like PHP and some questions about MVC?

Question

I don't mean to be controversial. Close if you see fit. But I've got to choose the best way to update my Intranet that's in Classic ASP. I've looked at umpteen framework, still looking and learning, but undecided. I know that PHP is still being updated and is a fine language, but I was thinking. If I wanted a framework couldn't I create and MVC framework with Classic ASP? I'm sure I probably could but that's not the point. I thought...I could do this or I could create pages with PHP with no framework and where would I be? Right back with the same predicament with Classic ASP, only a different language. This makes me think that PHP could be "dangerous" in my enviornment where everyone may not understand or "believe" in MVC. PHP would lend itself to the cowboy coding and mixing of layers quite easily. After all it's pretty easy to fire up notepad and just code without having to worry about layers and layers of "stuff."

My question: Is this true of all the platforms and languages? Are there any that are designed in such away that it would be pretty hard to fall back into the evil ways? The only thing I can see is one, ASP.NET MVC. It'd be pretty hard to start in that and end up not using it. Java EE 6. I don't know. I know Java has been pretty MVCish from long ago.

Thank you for any thoughts. I don't need to be lectured on MVC goodness. That's not my point. I just had an observation and wanted thoughts on how to keep my project MVC.

Answer 1

It depends. If you can see only one platform, namely ASP.NET, then probably this is the one you are most proficient with. Sticking with a familiar tool makes sense because it reduces development time, cost and the amout of bugs.

But ASP.NET MVC will not magically convert your teammates into OOP gurus if they truly prefer cowboy coding. The difference between classical ASP and ASP.NET is a lot more than the API and it is possible to write awful spaghetti code even with ASP.NET MVC. You can't cajole someone to sanity by prescribing a certain tool. Unless people in your environment understand the intent and benefits of Server Controls, OOP and modular code, you are going to see sad things happening even with ASP.NET MVC.

That said, you are probably better off using ASP.NET MVC compared to scenarious where you are not. Adhering to a specific coding standard usually makes things easier to understand, less error prone and more structured, no matter the language.

Answer 2

Just for the record. Nowadays, Classic ASP also have a lot of Frameworks including MVC ones like ASP Xtreme Evolution, Ajaxed, Troika.ASP and a lot more. There are good things in Classic ASP just like in any other language, as there are terrible things written in Java, Ruby, Python and probably in all languages. Before throwing yourself into a new enviroment, I would recommend you to read ASP a misinterpreted technology to notice that Classic ASP has a lot of good parts, including the Javascript ones!