Addons.mozilla.org to move from CakePHP to Django in 2010
micropipes.com
micropipes.com
For what it's worth, I believe a lot of these issues are solved with 1.2 (AMO claims to be still on 1.1 which is at least two years old now). It sounds as if their system is just defining relations in their models and letting the database layer pull up all the objects for them. Which of course creates problems. They should shift to using "contains" to limit the depth of the objects retrieved.
The only real issues I've run into in the most recent version of Cake have been an inability to define a separate join table on one of the basic relationships (hasMany?). I seem to remember rails making this possible through an intermediary table, but it is somewhat advanced in any case and the easiest solution ended up being to write an SQL function in the model and use that to fetch the data. It was not hard.
Good luck to them with the re-write.
Its too bad for such a high profile project to bail on Cake without giving the new version a try. It really is an excellent framework for many projects.
I worked at Yahoo and I’ve used different Java and PHP frameworks in the past, some good, some bad. However, that never stopped us from having a continuous build running locally and an integration build running on our server, or from unit testing our code, even though we had to extend and adapt some components and unit testing frameworks. The same with debugging, it never stopped us from creating awesome tools to debug our code and monitor the performance of our applications.
After finishing building a CMS using Django, I can only say one thing: A framework doesn't make you a better programmer. If you suck, you suck.
Good luck and godspeed on the migration, AMO.
It's about preference I guess: Kohana takes advantage of a lot of the PHP5 extra's and also unfucks some of the "gotcha's" CI had (especially in the area of loading stuff). Also it is updated more regularly and is community developed.
CI is still good, I personally prefer Kohana's way of doing it.
EDIT: Just realised that I'm asking you to sum up a lot to recommend one over the other. I'm currently looking at both in detail, cheers.
In terms of LTS: V2 is pretty frozen at 2.4 right now (i.e. no API changes) though the documentation still reflects V2.3. There should only be bug fixes on the 2.x branch. 3.x is in active development (and worth looking at) and should be there for the long haul.
I personally use 2.x because that is what I started with and I haven't had chance to make the switch to 3.x (it's pretty much the same except there are changes to some naming conventions and file paths) mostly due to having to support 2.x based sites still :)
EDIT: It's a bit old (and I apologise for the abysmal writing!) but this is a comparison I wrote when I first made the switch: http://www.errant.me.uk/blog/2008/06/framework-comparision-c... might be useful.
Seems like they have the resources to keep php and python running under duress.
i kid, i kid...