How do CakePHP frameworks and codeigniter compare with ASP.NET MVC framework?

Question

As a classic ASP developer about once a year since the advent of ASP.NET , I decided that I really needed to buckle up and explore this new trendy ASP.NET . A few days in work on codes, web forms and all that.

I decided that new trendy things are easy, and I’ll go find something else to learn (with PHP and Ruby and Python were all fun to play with but couldn't use it much with my existing ASP stuff ).

In any case, there was one project, and I was able to use PHP and CakePHP and, after sorting out MVC, I finally found what I liked and felt that it should be used on top of ASP PHP is cool too but it feels a lot like ASP, so maybe that why like it so much ). But now that Jeff and the SO team are raving about ASP.NET MVC , I think it's time to start messing with ASP.NET again, but

I keep thinking that PHP is free and blah blah blah. ... ASP.NET MVC much better than PHP with tools like CakePHP?

I know about compiled and non-compiled problems and performance issues, but most of them seem inconsequential when you consider all caching and the fact that you can compile your PHP if you want.

Answer 1

For a classic ASP developer moving into ASP.NET MVC, you are learning a new language (C # or VB.NET), a new database layer (ADO.NET), and a new structure (ASP.NET MVC).

These are many new technologies to wrap around you all at once.

Also, I don’t think it is so much that ASP.NET MVC is much better than CakePHP (or Code Igniter, Ruby on Rails, etc.). The great thing about ASP.NET MVC (and other ASP.NET technologies like MonoRail http://www.castleproject.org/monorail/index.html ) is that developers who use ASP.NET are now have the ability to follow the MVC pattern using the tools and languages ​​they are familiar with. This is an option that was not previously available.

Answer 2

Not too experienced with the Microsoft web stack, so I can't talk about it.

But I will say that as a web developer I was very disappointed with CakePHP. What bothers me particularly about this is that since it forces itself to be backward compatible with PHP4, it lacks most of the OOP design and structure that I'm used to. It all ends up being based on an array, not the state of an object.

Personally, after spending some time with the cake and being disappointed, I decided to put up with it and learn Ruby on Rails, which I am doing now. If you would like to stay with PHP, I would look at Symfony, but they are all really inspired by rails.

Answer 3

ASP.NET MVC is currently rarely documented - and, of course, it depends on your background. If you do not already know ASP.NET, I would not recommend entering it with ASP.NET MVC, too many levels of training at once.