In response to this recent post on four reasons to hate CakePHP, Matt Curry has posted some of his thoughts over on his pseudocoder.com blog to refute the comments made.

I'm still bored and lacking posting ideas, so I figured I'd give a hyper-critical breakdown of "Four reasons to hate CakePHP" by A.J. Brown. Let's get right into it.

He responds to comments on: CakePHP's "heaviness", the (in)flexibility the framework allows, alpha releases, changes between versions, no namespace considerations and its use of global functions.

You can see the original post here: Four reasons to hate CakePHP as well as his AJ's own response to comments he recieved - Maybe I was too hard on CakePHP.

In a recent post to his blog, Mike Bernat gets down to basics with one of the key pieces of functionality in PHP data persistence - cookies vs. sessions.

Knowing the basics of cookies and sessions is essential to any successful PHP programmer. It is useful to store pieces information on the users computer for later use. Things like when they last visited, language of choice, age, etc. Cookies and Sessions are the perfect solution to our needs.

He talks about both, including demonstration code to clarify some points and a chart at the end to compare their features, strengths, and weaknesses.

In a recent post to his blog, Mike Bernat gets down to basics with one of the key pieces of functionality in PHP data persistence - cookies vs. sessions.

Knowing the basics of cookies and sessions is essential to any successful PHP programmer. It is useful to store pieces information on the users computer for later use. Things like when they last visited, language of choice, age, etc. Cookies and Sessions are the perfect solution to our needs.

He talks about both, including demonstration code to clarify some points and a chart at the end to compare their features, strengths, and weaknesses.