I’ve been meaning to try Ruby on Rails, not because I like Ruby, or even use Ruby, but the Rails framework is supposed to be the big payoff there. But now there’s CakePHP (and other frameworks) that try to do the RoR thing in PHP.
Other than that little data deleting issue, CakePHP looks interesting, and I’ll dig in a bit deeper and see what it can do.
4 replies on “Looking at CakePHP”
I’ve said this before, and I’ll say it again. While you’re trying out other frameworks, I urge you to give Catalyst a shot.
I remember reading about Catalyst, and while I love Perl and use it daily, right now I’m investigating PHP frameworks. It still makes me sad to admit that PHP has more motion in the web app space than Perl does. :(
Come on man, of course this is bad, but we’re talking about a n00b-proof introductory example: it’s about implementing Cake, not HTTP best practices.
That said, in the off-chance that you plan to put your newly written blog app into production, you can add the following you your PostsController:
nate, you say “of course this is bad” but sadly, I mentioned it because I still see it fairly often. I just came off a project that did similar screwy things, and I continue to wonder, if people know these things are bad, why do they keep doing them? Best practices, eh? (Oh, and thanks for the code sample.)