On Nov 20, 11:33 am, AD7six <[email protected]> wrote: > On 19 nov, 23:41, jacmoe <[email protected]> wrote: > > > To me, a 'larger project' is simply a project with a lot of code. :P > > By that measure, a lot of truly awfully code constitute "large > projects". [1] >
I answered in the context of CakePHP. Sure you can write a large application using spaghetti code, but a great framework like CakePHP really helps you build that larger app, due to its MVC architecture. The larger the project, the bigger the benefit. :) I program in C++ mostly, and almost always use object-oriented programming and MVC for more involved projects. It has a slight overhead, but it makes it much more manageable. And your project is a lot easier to refactor / keep alive. > > It has less to do with how many users it has/gets. > > I disagree. You don't hit scalability, caching, concurrent, bottleneck > problems on a 'big' app which never has more than a few active users > at a time. I think you misunderstand what I'm saying: Scalability is a different matter. Sure, a framework built with scalability in mind helps a lot. And, yes: larger apps tends to use more resources. -- You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cake-php?hl=.
