On 7/1/06, Claude Schneegans <[EMAIL PROTECTED]> wrote: > > There are plenty of good reasons: > - any framework already developed and in the public domain may be far > too general > and may include many feature your own project won't need;
Features your project won't need? Not likely, as public frameworks tend to be generalized enough to only include the base components. Still, I'm interested to hear what you would consider a feature of FB, M2 or MG that a project won't need. - your own project may require some very specific needs that are not > taken care by the > framework, so you have to add it anyway. This is why frameworks are open-source, and tend to be extensible. If you can't extend it through a normal way, you can always change the core behavior. However, again, I can't even think of a reason to do it for the big 3 frameworks. For me, the first point is a major point. You waist more time horsing > around with things you > don't need that the time you save using the framework. Yes, you are still figuring it out for the first project or two you make with a framework, but for the 3rd project, or the 10th, things get a lot easier, sites get started faster, and you begin to find what truly reusable code is like. When you can copy and paste a group of features into a site you just started to give yourself a huge jumpstart, you'll be thanking whoever made that framework. -nathan strutz http://www.dopefly.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:245233 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
