The Underscore Archives

> I've been looking at Symfony now for a while and played about with it
> before going with it for any projects.
>
> It uses a model system called propel - which is an ORM that builds
> your database according to a structure you give it in a yaml file. It
> also has a nice tool commandline tool that can build an object mapping
> based on an existing DB.
>
> Overall Symfony feels right - nice build and deploy systems, good
> modules, supports a wide range of plugins and has great documentation.

The 'Cake VS Symfony' queston comes up a lot on the Cake google group.
Some of the basic reasons I went with Cake are:

- php4 or php5
- not dependent on any external libraries like PEAR
- can be installed by simply uploading a folder, no command line needed
- only 1 configuration required to get started (and that's only needed
if you're connecting to a - database), Symfony has a lot of config
files
- cake is faster
- Cake was written with RoR in mind
- cake has a very active community, and a very approachable dev team

basically, I really like Cakephp, it enables me to tackle projects of
a greater scope and in a shorter space of time without sacrificing
quality and it enables me to rapidly test my data model and get
started prototyping very quickly because of it's 'convention over
configuartion' mantra, which I could not do with Symfony.

Also some very prominent people are using Cake, namely:

IBM
Mozilla (FireFox addons site is cake)
~ loads of stuff by me :p

Seriously though, there was a big site built using Symfony for Yahoo,
their Yahoo bookmarks site, but by all accounts, Symfony couldn't cope
as it was, and the Yahoo guys ended up rewriting the framework to such
an extent it was no longer Symfony per-say.

hth

jon


-- 


jon bennett
t: +44 (0) 1225 341 039 w: http://www.jben.net/
iChat (AIM): jbendotnet Skype: jon-bennett