asp.net has got some convenient tools, but if you look deeper, you will see that it has got a lot of complexity, all that object generation, event binding with event handler methods, data controls are nothing special..

I develop using php right now, and I can tell you that its controls dont add much..There are too many tools that were put that dont add that much. Caching & dataset (all ado.net) might be useful in some specific sites..but they arent critical to use..you can use connected data transfer, and it works well!!!..

I had a look at mvc, that introduced the idea that you can generate html using functions (controllers), and unit testing, and friendly url, and no viewstate… but wasnt mvc inspired from ruby on rails? (thats what I read at least)..

I think that all asp.net is too convuluted.. I would rather to go to and stick with php. Asp.net tries to revolutionize the web development, but it never adds something new and revolutionary that is significant.. a language like php that has no tools like asp.net is still alive and kicking,,and no new gimmicks from microsoft will kill it..

It offers a better framework to put everything in.

Compared to asp.net it has it’s drawbacks.

Re-inventing the wheel is one of them.
Dirty asp-like spaghetti-code is another one.

The thing I especially don’t like is that while asp.net uses an object-oriented approach to the controls (server controls), MVC has gone back to procedural controls (html helpers).

And for me this is a step back in software design.
Many things are no longer strongly typed and error prone.

I’ve used MVC for a while now and frankly it’s been a disappointment.
While it has it’s uses for some things, for standard web-applications we will be going back to asp.net.

That is just not true. Just look at the post by P. Haacked on MVP Supervisor:

http://tinyurl.com/of7rm

ASP.NET MVC is really good, but you can’t use TDD as a pro over webforms development.

Why not fix it in the post? I happened to the read comments but most users won’t and you are grossly misrepresenting the facts and misdirecting the readers.

Thus, MVC is more like Classic ASP/PHP than Webforms.

That is, there isn’t an agreed upon way to do things. This is great in that it allows you to implement features in a way that makes sense for you and your application. But it’s also bad in that it greatly increases the learning curve and might make adoption of the framework a hard sell.

As an example, the ASP.NET web forms model has an easy to understand and easy to implement procedure for validation. The ASP.NET MVC framework…not so much. There are plenty of custom solutions out there which are arguably better than the ASP.NET web forms validators in that they allow you to hook into database events and put validation on your model instead of your UI, but again it comes at the price of ease of use. I can see developers being very reluctant to have to research and develop custom solutions for things that normally come out of the box in development frameworks.