The end of CakePHP?

Published on and tagged with cakephp

Today, Nate Abele, lead developer of CakePHP, announced in a cryptic tweet that he leaves the project. This comes shortly after Gwoo, the project manager, left the project, too. It seems like they started to work on a fork of Cake3 called “Lithium”. On Twitter people are a bit puzzled about those events, some even think it is the end of CakePHP…

I don’t know whether this will be the case, it is too early to say. But I doubt it. The project is still backed by the Cake Development Company, which employs some of the core contributors (Larry Masters aka PhpNut, Mark Story). That’s some guarantee that the show will go on. And of course there is a large community.

On the other hand I don’t know how many of the other contributors will remain. And the lack of (official) communication is also not that good for the confidence into the project. What happened? What will be the next steps? Who will take over those vacant roles? See also Matt Curry’s post on this matter.

Anyway, probably the best thing to do now is to drink tea and to wait until the dust settles…

Update (2009-10-23): an official statement has been published in the meantime.

20 comments baked

  • Tweets that mention The end of CakePHP? - cakebaker -- Topsy.com

    […] This post was mentioned on Twitter by TrinityByte, LucasRenan. LucasRenan said: #cakephp The end of CakePHP? http://bit.ly/22b90j (via @planetcakephp) […]

  • Fabio Cevasco

    Hell I wish this happened three years ago. I think the events speak for themselves: the Project Manager and the Lead Developer of CakePHP just left the project… That’s pretty much the worst thing that could happen to a software project.

    Well, all I can say is good luck to Garrett and Nate (and I really mean it)! I may even end up giving the fork a spin, someday!

  • CakePHP : signets remarquables du 14/10/2009 au 23/10/2009 | Cherry on the...

    […] The end of CakePHP? […]

  • Nate Abele

    I don’t really know what’ll happen to CakePHP. With a community of the size that it has, it seems “too big to fail”, of course that’s been said of organizations that are long gone now…

    In any case, Garrett, David, Alek, Jon, John, Matt & I are all looking very intently to the future, and to our (slightly postponed) launch next week. We’ll definitely keep everyone posted.

    And Fabio, thanks very much for the good wishes, it means a lot.

    – Nate

  • Nate Abele

    Oh, and Joël. :-)

  • The State of CakePHP | Ryan Rampersad

    […] the CakePHP world has been rocked. These few short snippets from various blogs around the web should illuminate what […]

  • Tarique Sani

    Had to happen…. Like Fabio I wish it had happened earlier! Am itching to get my hands into a Lithium based open source project ;-)

  • links for 2009-10-24 « undefined

    […] The end of CakePHP? – cakebaker (tags: cakephp) […]

  • Nik Chankov

    No one is irreplaceable as well as no one is married to a software project, people come in and go out. Every body has his own plans.

    Good luck to Gwoo and Nate.

  • Twitted by lyrixx

    […] This post was Twitted by lyrixx […]

  • Twitted by devzonefr

    […] This post was Twitted by devzonefr […]

  • cakebaker

    @All: Thanks for your comments!

    @Fabio, Tarique: Personally I thought the team problems (and with it a possible fork) were resolved at the time when PhpNut resigned as lead developer. But obviously I was wrong…

    @Nate: Good luck with the new project.

    @Nik: I fully agree.

  • snowdog

    Looks like I will have to start listening to my team and switch new projects to RoR. I really liked Cake…

  • poLK

    @cakebaker: yes, from my angle of view you are wrong in several things. A) PhpNut did not resigned as lead developer (lead change was done by other way). B) team problems did not stop even when Code Advisor tried to stay silent in edge situations able to damage project/community. I am sorry to say that, but my opinion is that resignation of Lead Developer and Project Manager should happen right after announcement of CakePHP core project, developed in secret for months without knowledge of nearby half of core development team, including Code Advisor.

  • cakebaker

    @snowdog: RoR is definitely worth a try ;-) On the other hand, CakePHP won’t disappear in the near future. So if you like it, use it.

    @poLK: a) Yes, it was rather a forced resignation, at least from what you could see from the outside. b) I don’t know what happened internally, but I agree with you that having secret projects in a team is not really good for the team spirit. From the outside, what irritated me most
    was that there were three different versions under development. I mean, if you have limited resources, then it just doesn’t make sense to work on three different versions…

  • Benko

    Hopefully this isn’t the beginning of the end. CakePHP is my goto tool for web development.

  • cakebaker

    @Benko: I don’t think CakePHP will go away in the near future. However, I think the mid- to longterm future of CakePHP depends on how fast the adoption of PHP 5.3 is.

  • CakePHP moved to Github! at code tunes

    […] two of the core developers, Nate Abele and Gwoo, left the project lately, many feared the worst. Now it’s different story! The CakePHP core team decided to move the project […]

  • Al

    Well I have tried CakePHP and it’s one of the most problematic and poorly explained frameworks I’ve seen. If they did a better job at explaining how to get going (instead of cryptic theory of how it works) I would have accepted it a long time ago. CodeIgnitor is much easier to get a grip of.

  • cakebaker

    @Al: Yes, I agree with you. The documentation is still a weakness of CakePHP.

© daniel hofstetter. Licensed under a Creative Commons License