If you are referring to 'scaffolding' then it is available in CakePHP as well (and RoR). I agree, this is a nice feature of a framework.
I have checked out Symfony as well (read through the documentation), and I still prefer Cake for the simplicity. Cake is dead simple - yet is very flexible and powerful. I have spent the last 2 weeks learning and diving into the API (version 2), and I love where it is headed. You have the ability for custom configurations in cake as well, its just not stored in an array of different config files.
Personally, I like the way that database results are stored in an array. This works great when you are working with multiple models that may have some of the same field types (or names). It also helps you keep things organized (at least for me).
PHP5 is one of the really nice things, but I program Cake with 5 as well (in my models/views) and it all works just fine. Cake started out in 4, and I think its doing a good job of managing both.
As for escaping output, I would agree - I wish Cake had this at the core. It would be very easy to add as a custom function or method - much like rails has h() for escaping their output. Maybe we will see this soon, who knows.
I would agree with you in that they are very similar in regards to goals and setup of the framework. For me, I am sticking with Cake due to simplicity - and I don't feel like spending 2 more weeks learning another framework when I have what I need now. hehe.f2富二代官网入口