Skip to main content

Problems with CakePHP - follow-up

Some people have responded including the Datepicker fame Marc Grabanski. So, this follow-up...

First of all, I was not ranting nor complaining; I've just blogged/documented my experience.

The common problem most of the people pointed out are that it scales for addons.mozilla.com. Those who have accessed their source code can understand that they've done lot of things and also the site is not database-intensive. You should really create a real database-intensive website to understand what I mean.

The other point that been pointed out is about open source and community. Lot of people may not be knowing that it's 2 people pushing it and don't want others to be credited. The generic model or dynamic model idea was originally been from grigri and Marcel. It's hard to be called as open source as only few and sycophants are driving it's direction (I'm not talking about svn access)

So, here are my humble checklist before you start shouting at me

  • Did you read and understand my post?

  • Can you code or at least read PHP? -- This is very important. My post is not indented for some naive people who want to create software in 2mins without really understanding the programming languages and tools.

  • Have you looked at the framework's source?

  • Have you tried to profile the code?

  • Have you witnessed the xdebug crashing due to deeper cyclic chains when you profile?

  • Have you created any application where you have to replace regexp calls to increase speed?

  • Have you optimized the DB and tried to scale a database-intensive site?

  • Have you referred the frequent discussion page? (It was originally created by me and I have contributed to the most of it) -- You'll hit that page only when you create webpage and get into problems. I have a strong opinion that some sycophants and Evangelist aren't using CakePHP at all. (Evangelist is always trying to sell his "intellects" with philosophical/unscientific remarks and bootlicking some naive people whom intern want networking. Note, this is not a flame, but my strong opinion)

  • Have you read codes of cakebaker, ad7six, grigri, franky, baz...? Do you think, they have a better fork with them?

  • Have you removed some/many automagic things? or Have you used it just for dispatching?

  • Have you checked source of Akelos, Solar, CI or fase?

  • Finally, have you read Rasmus's Simple is Hard?



If you answer "Yes" to most of the above list, you may be with me.

And, at this moment, like I mentioned, the state of my mind is that, the need for the contemporary world is to have a better toolkit, which I believe could be developed with good readability, coding standards/practices, scalability and simplicity.

Update (2008-09-06): My apologies for Chris Hartjes, who found the post to be personal attack on him. I understand that I could have used better wordings.

Comments

Anonymous said…
"Evangelist is always trying to sell his "intellects" with philosophical/unscientific remarks and bootlicking some naive people whom intern want networking. Note, this is not a flame, but my strong opinion"

Ouch.

If that's not a personal attack on me, I don't know what is.

For the record:

* I use CakePHP for all but one of my current PHP projects (I inherited a PHP project started with Code Igniter)
* I don't think I have anything to gain by "bootlicking" people in my blog posts
* I agree that there are parts of CakePHP that need improvement
* Rasmus' "Simple is Hard" presentation is awesome, but "Hello World" comparisons of frameworks are irrelvant
* Other people's egos have gotten in the way of making positive contributions to CakePHP, which is sad but understandable
* I'm interested in YOUR thoughts on how to make CakePHP a better toolkit, short of a complete rewrite
Anonymous said…
This comment has been removed by a blog administrator.

Popular posts from this blog

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and...

Interview question #2

This is related to PHP's array . An array has number of elements. All elements are integers and unique, which means there is no repetitive integers. (e.g.) $foo = array(7, 5, 9, 13, 2, 8); You have to sort the array, provided: You should scan the elements only once. You're not allowed to compare the elements when sorting. (i.e., you're not supposed to use any comparison operators) Sorted resultant array may not be the source array. How will you do that?

What's wrong with delicious.com?

The recent UI changes of delicious.com is quite confusing and smells suicidal phase. I have noted that, after Joshua Schachter sold it to Yahoo!, it's going crazy changes. Probably, it's because a Yahoo! company now or Engineers don't get the real idea? Some crazy moves: del.icio.us to delicious.com change; probably to reach countries that censor .us TLD? delicious.com to www.delicious.com; unjustified Perl to PHP switch; why? for:handle geekish way to share to separate box; crazy but ok. Looks like, the new Yahoo! guys don't know how to make it a cult following like how twitter popularized @handle Recent broken UI