I've used CakePHP for a lot of projects now. There's no comparison to Ruby on Rails. Rails is smartly integrated, well-designed, and sits on top of an elegant language. CakePHP is an admitted ripoff of Rails that sits on a popular but terrible language. It copies Rails - almost randomly - without copying any of the stuff that makes Rails great. And PHP is a language plagued by indecision, delays, and paradigms from the last decade.
What makes Rails great?
What makes CakePHP awful?
Cake doesn't even try to hide the fact that its cloning Rails in PHP, but it's at a disadvantage from the start because PHP's syntax is just so much worse. And they use arrays to represent objects. And PHP's array syntax is terrible. Unbelievably terrible. Which makes the decision to go all-in on PHP arrays baffling. I spend the majority of my time in Cake trying to manipulate arrays-of-arrays-of-arrays-of-arrays that are supposed to represent some kind of shoddy struct, then mangling with model associations that require about 5 nested arrays to define. Add to this the fact that CakePHP tries to "innovate" its way around some of its shortcomings in a less-than-brilliant way (like, um, $recursive) and you get a steaming pile of garbage that's only marginally better than just coding a PHP project from scratch.
Rails's smart design has come at a cost. In the past, they haven't been shy about breaking backwards compatibility, sometimes in a big way, to cut out cancerous ideas before they take hold. It's a community that acknowledges mistakes and embraces their eradication. And Ruby is an elegant language with strong design and is under active development. PHP on the other hand has languished for years, most notably with a critical security bug called $register_globals. On top of that, they've been slow to introduce object support, type-checking, and sometimes make terribly confusing decisions (like the decision to call a feature overloading that has absolutely nothing to do with method overloading in the traditionally accepted sense of the word).
To be fair, here's what I don't like about Rails (and Ruby):
Cake php sucks. Still asking why? Their examples are difficult to understand. They have 15 minute tutorial but setting up instruction will take you a day and you will realize that their instructions are not that helpful.
With CakePHP you sooner or later arrive at some undocumented dead end where nothing works, and nobody can tell why. It is in my oppinion a complete waste of your time.
Someone say's that cakePHP is a ROR clone. Hmmm… I would see where there is a ROR style in this piece of shit !
I spent a long time working with CakePHP. I spent more time fighting with it than getting benefit out if it.
Hi Peter, how are you.
Can you help me in building a recipe website.
have you seen the website tastespotting.com, foodpair.com
I really like the pattern n formats instead of the regular stuff and then use the header in two lines for the rest of categories.
Just a heads up
I looking frwd to a website and mobile app for all OS n tab with
Compulsory registration which cld be possible from all possible social networking sites Users should be able to register any how in any which way possible, by a standard email process OR through social networking sites like FACEBOOK TWITTER LINKEDiN PINTEREST and all such sites also if possible Registration through mobile phone shld be made available.
Mobile Apps shld not have much of a difference than the main site.
International Payment Gateway shld be user friendly with emphasis on internet banking and any visa master or gift n all possible debit cards and could be added n if IMPS like Mpesa can be added.
The Recipe Management and Socializing Application shld allow registered users to view unique recipes of other individuals who are passionate about cooking.
HOWEVER the recipe management application shld only allow cooking enthusiasts to share edit existing recipes and repost and promote recipes by email they would like others to prepare and enjoy with their friend and families - ONLY if they make specific payments.
Cakephp is awesome, if any issues contact me.
When I run the command, “cake bake”, why does it not go into the cake shell? It runs it, then I'm back to the dos prompt?
cakephp is a piece of shit, maybe? I dunno , can't get the f****ing shit to work properly to actually assess it. All the tutorials are out of date.
This article is 7 years old now and where is Ruby? Nowhere to be found. And where is PHP? Everywhere. Good luck finding a job coding in Ruby or even Python. You'd be better off learning ColdFusion. LOL
I'm not sure what point you are trying to make? There are a lot of things you could criticize this ancient post for (and you could've easily sounded smart, since you are talking to someone in 2010), and I would've wholeheartedly agreed with you on. But PHP was a garbage language 7 years ago, and CakePHP was always a garbage framework. Nevertheless, this wasn't a prediction of doom for PHP. For what its worth, I'm gainfully employed at a Ruby startup today, and doing talks in the local Ruby community.
But if you're going to make random unfounded claims, PHP has been on a long slow decline for more than a decade:
Hello, can I know where I can find those statistics of interest from? Thanks
Google Trends brother
If someone says CakePHP is great, he is a piece of shit.
I removed your other comment because it was a racist piece of garbage. I approved this one because it was merely garbage.
I agree. CakePHP is just a shitty framework!
- it is monolithic, absolutely **not born to be scalable**. Pretty funny when your app starts having billions of hits and you're forced to buy custom private clouds to run something that could be done by a single php page.
- it's **incredibly slow**. Recent versions of Cake are still the slowest frameworks I've ever tried compared to almost any other framework.
- it has **tons of lines of code**. Some developers don't care what's going on under the hood; I like to be able to quickly find out how/why something doesn't work the way it should. But it's code is so much that finding a glitch can be overwhelming.
- it has a **ridiculous namespace organization**. It implements lazy loading in the form of App::uses. This is, IMO, clumsy and no better than doing a require.
- it has a totally **inadequate documentation** leaking in every aspect, not even approachable as a real documentation. It looks more like a cut&paste archive of Pastebin (http://pastebin.com/). So finding something on the documentation becomes a nightmare, while it should help you saving your time.
- it **does not support default routes** for fancy/custom urls unlike ANY other php framework. So while crating urls, you are required to update the default routes. This sounds a bit ridiculous in modern web application development.
- **migrating from version 2.x to 3.x of CakePHP** it's a complete nightmare and nearly impossible to do in most of the cases. Pretty insane for a self-defining backward compatible framework…
I could keep on writing an endless list of horrific things about it; it's enough to say that IMO **it is the slowest, most confused, and worst framework I've ever used in 27 years of professional development**.
**People should delete it from the Internet** instead of magnifying it just because it makes possible to build insecure and bad-performing apps to noobs and totally incompetents. Not to mention self-defined programmers whom could not write a framework in an entire lifetime.
Why don't you use Nette? https://nette.org/
Why don't you use zend?
cakePHP sucks. Why? Their own blog tutorial - ambiguously written - results invariably in error messages:
Error: PostsController could not be found.
Error: Create the class PostsController below in file: appcontrollersPostsController.php
If those idiots cannot write out a simple “hello world” tutorial … one wonders what else they punted on.
PHP is an old, old friend. codeigniter is not, but at least it works out of the box and is documented by humans rather than imbeciles.