There are reasons why someone would choose CakePHP and why someone would choose Rails.

Besides, since CakePHP is a close clone of Rails if you know one then you pretty much know the other.

Suggested reading: Patterns of Enterprise Architectures by Fowler. It gives a coverage of “architectures” and “patterns” without specifying any particular language.

RoR is not nearly as complicated/expensive to host now as it was a couple of years ago. One of the easiest ways to run Ror is to use Litespeed (www.litespeedtech.com) on a cheap VPS like Slicehost. Their ruby gem makes running RoR apps a piece of cake (pun intended) :)

Cheers

Dynamic languages and all is nice, but come with a price (performance).

I’m migrating apps back to PHP (therefor not cake for that matters), but surely RoR tought me how to program things the correct way.

You can’t directly do something like that but I believe you can do something like that using the magic method __call()

From the manual:
“The magic method __call() allows to capture invocation of non existing methods. That way __call() can be used to implement user defined method handling that depends on the name of the actual method being called.”

I work with php but don’t use the CakePHP framework (or any framework for that matter) but I just wanted to set this straight ;)

Feel free to use what you want…

isn’t it supposed to be “then throw it back to a function” ?

regards,
Best

Actually you can set the recursion in data retrieving, and unbind model if necessary. You can make your own query, set foreign key, use transactions .... etc... Of course you have to know the framework you're using to get the best from it, and here i think the cake docs and api lack something. Often i had to look directly into the code to learn/understand ...!!

Anyway ... the 1.2 version is a big update and have lots of features... :)

A lot of self-appointed Rails "critics" knock down arguments that nobody in the Rails community, as far as I can see, ever really makes (i.e., the idea that Rails somehow invented Active Record or MVC design patterns, or the concept of scaffolding). Rails certainly has its drawbacks, but most of the ones I can see -- a sublime ignorance of all but the most basic features of an SQL database (no real concept of foreign keys, and rather egregiously, no way to use prepared statements), and an extremely rigid "follow our conventions or we'll make your life miserable" mentality -- are ones Cake shares. (Cake's database handling is, if anything, considerably more brain-damaged than Rails' is, from what I can see: it has no concept of "lazy loading," and it's quite possible to create a scenario where you're trying to get a 'table of contents' listing from one table but, because of associations, Cake will by default load in pretty much the whole damn database..)

CakePHP is doing a great job as a framework alone - not being a Rails clone. The following 1.2 release will come with features that Rails doesnt have neither plans to implement.

Also, design patterns are not copyright of Ruby On Rails. MVC, ActiveRecord, Scafolding... So, now if a framework implements this, its 'another Rails clone'? Shhh...

http://www.badrit.com

Yes, it did seem pointless and a little daunting to ditch PHP and start again with Ruby but, after making the switch a year ago, it was well worth it. Why? Because Ruby is more powerful, easier to read and fun to code. And easy to learn!

After all this time, I still have to check the argument order for many PHP commands (eg usually it's command([needle], [haystack]) except sometimes it's the other way round). PHP requires a lot of memorising, whereas Ruby does not (well, much less anyway!)

Ruby has a lot more to offer than "puny features" - give it a go!

regards,
diyana

at http://www.akelos.org

check it out.