I wouldn't say Cake is _bad_. I've used it on a fairly large project and wasn't
horrified by it - but maintaining a Cake app is a LOT more work than creating
and maintaining a Symfony app.
Work === time === money.
This is chiefly because Symfony has a lot of additional helpers, and auto
I'd second what Pablo said. You can always get a list of reasons for or
against a framework.
In the end, if the client can support Cake but not symfony, then i'd just use
cakephp.
CakePHP is pretty easy to develop in. If you can develop in symfony, cakephp
will be... cake :)
-d
On Dec
Hey guys,
We've specced a project here for Symfony, and the client has come back
saying they want to use CakePHP instead because someone there end has
used it, therefore can maintain it.
I've heard CakePHP isn't one of the better frameworks, but I haven't
used it so I don't know why.
What we
Hi Stephen,
As much as you may not like it, I think you should do what the customer
asked. If they have someone already that can (or think that can) maintain
CakePHP, for the customer this is very important.
There are many reasons why not use CakePHP, but there can also be many why
not use
