For me, CakePHP is cool and easy to use...once you are able to understand the concept. The baking capability is quite amazing. I was thrilled the first time I used it. (FYI...CakePHP is the first and only framework I have used). I started learning PHP back in July and after few weeks on PHP, I was given a project to work on using CakePHP.
But one thing guys in my company complain about is the steep learning curve. I know of two friends who dropped CakePHP for Laravel. What they said was that Laravel was easier to learn than CakePHP. Their reason; Laravel's documentation is easier to understand than CakePHP's. One of them even said Laravel's documentation helped him understand some of the things he read while learning CakePHP. And from my own experience, they are right. There were times that I found it very hard to understand some concepts of CakePHP. Naturally, I am a tenacious person and I have a knack for learning complex things hence, learning CakePHP is not much of a problem for me. I remember telling a friend I was learning CakePHP, he sighed and asked me what the learning curve was like for me. He also shared his experience on how hard it was for him to learn CakePHP and how he eventually dropped it. My point: Though I haven't had the time to try out other frameworks, I would suggest that the Cake guys look into how to make the documentation a little more friendly. As for the war among frameworks, the most important thing is using a framework that meets your peculiar needs and gets the job done in the best way possible. So far CakePHP hasn't failed in that aspect. On Monday, 29 September 2014 22:15:54 UTC+1, Florian Krämer wrote: > > In the official CakePHP Facebook group Yanuar Nurcahyo asked about > opinions on that link > http://www.quora.com/Why-isnt-Cakephp-popular-despite-being-one-of-the-earliest-php-framework-to-be-written > > I'll quote my own comment I've added to that posting: > > I'm a little shocked about the wrong information people spreading there as >> well as the amount of false information. Especially the one that got 4 >> up-votes. Most of the answers there read like FUD or written by people who >> can't or won't read documentation. Also I really don't get why people >> always "need" bleeding edge php support. There is no urgent need or do >> you migrate you app / server to a new php version just because it's cool? >> The only problem that CakePHP has is an image problem. > > > What I would like to discuss in this thread is reasons and solution to > them. Why has CakePHP such a negative perception? The thing that bothers me > personally the most is why the *uck do people say it has a bad > documentation? Seriously, I don't get it. Can't they find the > documentation? Can't they use it? Or is it really just FUD by some > <random-framework> fanboys? > > The "stone age php version" isn't a very valid argument IMHO. Yes, I > agree, CakePHP felt behind other frameworks for at least ~2 years and I've > missed the namespace support more than one time. But that was really the > only language feature I was really missing. Everything else is sugar on top > of the cake. I don't know if other people update their servers and apps for > fun and if they do the required testing for free for their clients...but > well, looks like some guys out there have more a cowboy-coder attitude than > a professional one. > > Also I don't get why people complain about the architecture of CakePHP, > yes it is different, yes it gives you everything out of the box and isn't a > package made of 100 loose libs and then glued together. This is IMHO > actually an advantage and makes it easy to get started with it. And > seriously, how often do you change the ORM stack of <random-framework> in > reality? And on top of that, CakePHP 3.0, as far as I can tell, is more > decoupled than 2.0 was. For example the face pattern in Laravel is, as far > as I've worked with it and understood it, just one way you can use for > dependency injection. The face seems to works like a proxy. I might be > wrong, I haven't spent much time with it yet. SF2 is using a container > object to deal with the dependencies. However, my point here is other > frameworks *appear* to be more fancy and by this attract people who are > looking for fancy things, "interesting" design patterns and architecture. > Which brings us back to the cowboy-coder attitude. Something doesn't has to > be fancy to just work. > > I know that for example Symfony gets a lot attention and exposure through > having virtually one domain per component of their framework and a nice > design for these sites and for whatever reason Symfony manages it somehow > to get massive funding. Creating all these pages and a fancy design takes > time and money. So I don't think doing something similar would be an option > for CakePHP. Honestly I have no ideas what could be done to help making > CakePHP look better (and stop these silly guys from spreading FUD). I would > not mind all their critics at all if they would bring valid and detailed > arguments. But everybody complaining about CakePHP is just repeating other > peoples FUD about a bad documentation and not exactly mentioning what is > wrong with the architecture. Going into a discussion is like going into a > fight without a weapon. But well, the problem here is nobody fights these > false "arguments". :( > > I personally don't mind using Symfony2 or Laravel, they're good frameworks > as well, but I don't think that CakePHP 3.0 has to hide in any aspect, nor > had Cake2 when it was new. But CakePHP has a completely different > philosophy than SF2 and Laravel, obviously one that people are not used to. > > So, has anyone constructive critics about that? Maybe others here don't > even think CakePHP has a problem with it's perception? > -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/d/optout.
