Well, I’ve been getting a good deal of on-the-job Rails practice, and am appreciating how well thought-out the framework is more and more. In contrast, CakePHP is missing a vast number of features. But it’s still quite promising. I’ve decided against playing with Symfony for now, as it’s annoyingly complex and just doesn’t feel right for me. Akelos fell apart when I tried to build the demo blog.
Cake’s bake utility is vaguely useful if only for the fact that I don’t have to memorize 3 lines of code. I’m much more interested in learning how to use the Cake console, as that’s one of my most-frequently accessed parts of Rails. Any time I need to learn something, I dig through mysql to find out field names, and dig through console to quickly see exactly what format data will return in, etc.
I’m glad Cake uses associative arrays rather than simple argument lists, that’s for sure. However, the 1.2 validation, though more complete than pre-1.2 validation, seems to be one of the more unnecessarily complex pieces of Cake functionality. It can be treated more simply, though, which is great.
Next up on the Cake learning plate: caching, testing, and ACL.