Comments on: CakePHP: Is It Truly The Best PHP Web Framework?

By: benny l.e.p

benny l.e.p — Sun, 30 Jan 2011 16:21:36 +0000

cakephp it’s easy , i agree it’s lack of documentation but if you dig further, you will never look in to another framework, if you need advance documentation you should look in http://api.cakephp.org

By: pawan sharma

pawan sharma — Tue, 22 Jun 2010 13:13:46 +0000

hello friends,

I love Cakephp.

i want the best e-book of CAKEPHP e-book with project practice.
if you have please send me. My email is pawansharma13@gmail.com.

Thanks

By: Jeremy

Jeremy — Sat, 14 Nov 2009 12:42:55 +0000

I don’t understand combining both php 5.0 and php 4.0 compatibility for any one framework. Couldn’t they split into two parallel frameworks or even 2 separate projects? One for 4.0+ and one for 5.0+ (or 5.2+)? That way the 5.0 /5.2 version could support PDO and 4.0+ version would just use the older data connection methods. This could keep the size and complexity down among many other improvements.

By: Dave K

Dave K — Fri, 21 Nov 2008 03:55:39 +0000

I just moved companies and the new joint is all PHP, I came from a place which evaluated a bunch of technologies and eventually settled on Django and now I’m spending time evaluating PHP’s various frameworks and I’ve got to say, compared to how easy Django is most of the PHP frameworks seem very immature and incomplete.

By: Jim

Jim — Sun, 21 Sep 2008 15:29:16 +0000

Cake falls short on the “intuitiveness” part of a framework – you have to go to the docs for everything, since there doesn’t seem to be much of coherence to the syntax or the structure. Additionally, the routing model leaves a lot to be desired, and CakePHP templates look like the ugly inline PHP we’re trying to avoid in the first place.

If you are serious about finding a framework that’s actually going to decrease your development time, even in the beginning, it’s time to look at the Fuse PHP Framework. Built to have a low barrier to entry while maintaining the features you actually need (user authentication, simple but extremely robust templates, easy data access, etc), it’s the only PHP framework you’re going to need. Here are some reasons why:

http://jimkeller.blogspot.com/2008/09/why-you-should-do-your-php-development.html

By: Remo Harsono

Remo Harsono — Tue, 17 Jun 2008 11:57:09 +0000

Probably the worst part of CakePHP is its documentation for new CakePHP users. I think CakePHP Documentation Team should learn from what PHP Documentation Team has done to new PHP users. I think PHP has grown so fast was not only because of its easy to learn scripting language but also very very good documentation especially for new users (like me).

By: Salman

Salman — Fri, 23 Nov 2007 10:04:00 +0000

I am reviewing many frameworks and PHPCake seems to be a nice one.

By: derek

derek — Sun, 21 Oct 2007 22:50:08 +0000

Symfony works PHP5â€™s PDO class library and this in not supported at cakePHP since cake supports PHP 4 as well..

By: AceMacaro

AceMacaro — Fri, 24 Aug 2007 06:23:00 +0000

Never known any framework, my code in php are disgusting. I have to write all the codes at the upper section of my .php.
I been learning cakePHP for a week now, and at first its kinda frustrating,
for lack of documents, newbie examples and the list of functions available. (Thanks to donutczar for his helpers example, it helps a lot).
Anyway, it is hard(after a week of reading), but now i currently developing a web payroll system, yup, “RAPID DEVELOPMENT” is the right term. but still it slows me down, cause i need to read(manual) or ask question(forums and #cakephp) once in a while. Cakephp helps me alot. The team says “it was easy”, some says “it was hard”. I trust the team and continue learning.

By: kuman

kuman — Sat, 18 Aug 2007 00:16:14 +0000

I tried my hands on CakePHP once (about half-year ago) when I was evaluating a few frameworks for my project. I didn’t appeal to me coz it seems awkward to have to define the data relationships. I wish it had some kind of tool to read from the database and generate the model classes. Defining the relationships by hand is ok at the start of the project but what happens when you wanted to make changes to them (I know some would say you can use the scaffolding features before really committing/translating the relationships to the db schema but imagine if you’ve done all that and at some point decided to commit to the database and a few months later have to modify the relationships, will the changes be easy to make?). This is one of the reasons that I had to choose Symfony over CakePHP. Don’t get me wrong though, that was the only reason I decided not to go with CakePHP. I liked it’s every other feature.

By: Mark Crane

Mark Crane — Tue, 26 Jun 2007 16:40:30 +0000

CakePHP looked interesting until I found it didn’t yet support PDO (PHP data objects). If CakePHP is the most popular framework that scares me a bit since it is a slow on supporting PHP 5 features ie PDO that has been available for approximately 2 years. Without PDO the database options are pretty limited in CakePHP. Until PDO is supported in CakePHP I will pass.

By: Dustin Weber

Dustin Weber — Sat, 17 Mar 2007 06:18:40 +0000

Taking advantage of the scaffolding is definitely a hugely powerful aspect of Cake (and other MVC frameworks that offer scaffolding). It can really save some time and effort in the pre-beta stage.
- Dustin Weber

By: Anonymous

Anonymous — Mon, 12 Feb 2007 03:18:59 +0000

The scaffolding can come in so handy. It is the best part of whole thing. I use it often,.

By: Dustin Weber

Dustin Weber — Sat, 10 Feb 2007 20:25:34 +0000

Yeah, I'm down with it. I've known it's power ever since I started tinkering with Rails, but hadn't truly applied it in the PHP arena.
I think it'll work out swell.
I haven't passed on Ruby either, just isn't a viable option for my work setting right now.
Outside projects are game-on though! So hah!
- Dustin

By: Anonymous

Anonymous — Fri, 09 Feb 2007 13:40:50 +0000

Glad to see you're getting on the MVC bandwagon. I won't give you quite as much grief for passing on Ruby now.