Module support?

This would be soooo powerful

Some people that are voting "NO" call the others bad developers that don't know how to build web applications. They say it would be as simple as put the functionality you want in libraries.

Of course everything can be done in anyway... I hate "religious" talks. We have those people that say PHP sucks and compare PHP to RoR instead of Ruby... We have those people that say that WordPress sucks because it's not MVC and blabla..

For me, the modular approach is as important as using functions or classes. Why would you need to write a function if you can write the code over and over again?

As far as I can see to use MVC in an efficient way your app would have to be like:
Controller -> Model -> View
This means that you lose all the flexibility and organization of your application. Of course if the idea is to have only very simple controllers and models and views it will work fine. I might have:
/account/edit/user_id
And then the project owners decide to have one extra route that will contain exactly the same as above but also a bunch of other functionality from other controllers of your application. Eventually other functionality that need information about other controller. What will we do? Tell the project owners how we want to build the application?

Life is always changing, all should be modular, nothing should be put on extra large files, libraries aren't enough. In fact with HMVC of Wired you can have libraries, configs, and so on... inside a module. This itself can lead to more selfcontained code and force more organization of your application. I prefer to have something working good then something that is supposed to be a certain way just because it's more pure or whatever.