Well...I just know my own experience. You seem to be assuming that the Developer who would be taking over the site, and updating it, maintaining it etc. is familiar with the framework.
I am assuming that they are not. So in addition to figuring out your specific application, that developer must become proficient in the Framework that was used perhaps BEFORE even touching your application. Another consideration is that you use a Framework that is popular now. What happens in 3 or 4 years when it is not popular anymore? You have moved on from the application, and someone else is coming in to take it over. Will they be able to find documentation on the framework that you used 4 years ago? Will the site still be up? Will the framework be accessible? Will the community support options still be active? Can you find information on Fusebox 3.0 at the fusebox site easily now? Or is most of the information all about the latest versions? (Just as an example). I am not advocating spaghetti code. But you can easily implement your own MVC architecture quite simply for many websites. Embed decent technical documentation via code comments, and someone who comes after you may actually have less work to do. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-community/message.cfm/messageid:327155 Subscription: http://www.houseoffusion.com/groups/cf-community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-community/unsubscribe.cfm
