Comments on: Why I Prefer Ruby on Rails over CakePHP

By: Michael Clark

Michael Clark — Thu, 16 Apr 2009 23:30:47 +0000

As Ben pointed out, you can also use the afterFind to inject generated fields into the returned results array without too much trouble, so you might also want to modify that section of your post – while Cake may not yet be quite as elegantly used as Rails, it does seem to be beginning to acquire it’s most popular features — now it’s still lacking the object over array find result – but it’s much closer than it was.

By: Jimmy'z

Jimmy'z — Fri, 29 Aug 2008 22:27:32 +0000

Ben,

This is great news for the Cake community. I’ll update my article.

–
Jimmy

By: ben

ben — Mon, 25 Aug 2008 13:34:36 +0000

You can also now do reverse routing with CakePHP. Using your /person/view/id example we can now do the Rails like $html->link($persons_name, array(’controller’=>’person’, ‘action’=>’view’, $persons_id);.

By: Mike H

Mike H — Thu, 07 Aug 2008 21:54:44 +0000

With Cake 1.2 there are now model behaviors “Bindable” and “Containable” that allow for pretty accurate manipulation of what your model retrieves on recursive queries, so no more uneccessary data retrieval.

Also, data manipulations like concatenation of the first_name and last name can be integrated into your model data using the afterFind() function in your model.
Very quick and easy.

By: Baz L

Baz L — Mon, 07 Apr 2008 13:56:09 +0000

One thing I’m confused about…Automatically querying data in the view? Unless I’m missing something, I wasn’t able to get this to work. Always got an existence error, unless I modify my find in the controller…

Please enlighten me.

By: mbavio

mbavio — Thu, 03 Apr 2008 13:50:38 +0000

Better late than never…

http://bakery.cakephp.org/articles/view/bindable-behavior-control-your-model-bindings

Read that article, then write tihs post again.

Cheers,
mbavio

By: Jimmy'z

Jimmy'z — Fri, 15 Feb 2008 15:52:39 +0000

I’ve looked into the Zend Framework, but I haven’t used it on a real project.

Cake and Rails both follow a principle of “Convention over Configuration” which makes them a bit less flexible, but very easy to get up and running and to maintain. Zend Framework requires a lot of configuration, so you will spend a lot of up-front time getting your configurations right rather than building your core software.

Some people see Cake and Rails as a bloated framework, but I think their benefits far outweigh the costs of a large framework. Rails has cut down the bloat quite a bit in v2.0 by pushing a lot of the functionality into plug-ins. However the plug-in structure is really easy to maintain.