I'm sure you'll get a number of responses from people familiar with
both systems, professing that CakePHP is better / smaller / faster,
whatever.  I haven't used Zend, so I can't comment on that.

However, the reason I am going to stick with CakePHP is because I know
it, and trust its direction.  We have already invested a couple of
years in learning CakePHP, our team is familiar with it, and it is
providing us with substantial benefits over using no framework (or the
custom "framework" we used to use).  I can't remember the last time we
had a business need for a site that we couldn't solve because of
CakePHP.

So basically:
I know CakePHP
It can handle anything I want to do
It is driven by very strong developer(s), who have a proven commitment
to quality.

and that's enough for me :)


On Dec 17, 2:59 pm, Action <[EMAIL PROTECTED]> wrote:
> I've always used Cake as my primary framework, but the Zend Framework
> seems to be shaping up nicely. Most of its published criticisms have
> been dealt with since 1.0 and it has some very impressive features
> (webservices, etc.).
>
> Given the fact that it's "Zend" and that there's an entire team of
> professional developers behind it, do you think this framework will
> become the industry standard for PHP? Also, do you think other
> frameworks such as CakePHP will die off as a result?
>
> The reason I ask is because I question Cake's future. I've already
> spent a lot of time on this framework, but I don't want to waste time
> if something like Zend is going to become the standard. Cake's
> releases are far more infrequent than Zend's and Cake's documentation
> is STILL horrible.
>
> What do you think?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to