CakePHP shines when developing *web applications*. IMO, there are much better tools out there that do *sites* and do them well.
However, anytime you need to add something customized, that's where CakePHP comes in. Also keep in mind that there's an entire slue of caching that it does. However, I'd have to agree with MG. Development time is where it's at. On Feb 8, 2008 7:28 AM, MonkeyGirl <[EMAIL PROTECTED]> wrote: > > Hi! > > To be honest, rendering pages quickly is not the advantage of CakePHP. > Any site you've made by hand is inherently going to be faster than one > that's having to check, say, what columns are in the database's tables > each time you pull something out of them. > > The reason it's still very much worth using CakePHP despite this > slowing down of a site, is that it *really* increases the speed of > actually typing in the code to make it. If people are more expensive > than computers at your company, then this is why they should consider > using it - being able to make sites quicker than they could make them > before, even if the individual pages render a little bit slower. > > You can even buy a faster server instead of hiring several more people > to do the grunt work of making the new sites, because the computer now > does that for you. :) > > This is all comparing CakePHP to no framework at all, mind. All that > I've said is probably true of all frameworks, though. > > Hope that helps, > Zoe. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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=en -~----------~----~----~----~------~----~------~--~---
