By WJ on
From Wikipedia, it looks that MVC helps long term coding development. I'm not very sure if MVC can make a significant difference with long term web development.
But, when upgrading versions, the users have to wait modules of new version for a long time. It seems often that modules of previous version can not move forward within a short time with the core program. The time lag creates hesitation to use present version and the new version. Isn't it a waste?
My questions are:
1. if MVC matters with web development, why for yes or no?
2. if Drupal has a MVC framework?
3. is there a page for users to know how many modules for version 4.x and how many for version 5.x?
Comments
Interested
I'm a bit interested to see what some of the other developers have to say about this. I would point out that the main reason for contrib modules taking awhile to work with the newer versions is just the commitment of the relevant module's developer(s). Most modules could probably be updated in a day or two or less, listening to one of the lullabot podcasts they've suggested usually 1-2 hours usually. Of course some of the more complicated modules like ecommerce will need more time, but they are also expanding the development not just upgrading the existing code.
I can also answer your last question, if you look at the modules page, you can easily filter modules by which version they apply to.
--Ryan
www.ryancross.com
www.jamescrossinc.com
--Ryan
Ryan Cross
James Cross Construction Services
Project Management Software
A little research
I decided to check the forums to see if anyone else had discussed this and came across some good threads.
http://drupal.org/node/38191
http://drupal.org/node/45798
http://drupal.org/node/41508
--Ryan
www.ryancross.com
www.jamescrossinc.com
--Ryan
Ryan Cross
James Cross Construction Services
Project Management Software