CakePHP vs Hoodie: What are the differences?
Developers describe CakePHP as "The Rapid Development Framework for PHP". CakePHP makes building web applications simpler, faster, while requiring less code. A modern PHP 7 framework offering a flexible database access layer and a powerful scaffolding system. On the other hand, Hoodie is detailed as "A fast offline-first architecture for webapps. Super-simple user management & storage. Great for mobile". We want to enable you to build complete web apps in days, without having to worry about backends, databases or servers, all with an open source library that's as simple to use as jQuery.
CakePHP and Hoodie belong to "Frameworks (Full Stack)" category of the tech stack.
"Open source" is the top reason why over 34 developers like CakePHP, while over 3 developers mention "JSON" as the leading cause for choosing Hoodie.
CakePHP and Hoodie are both open source tools. It seems that CakePHP with 7.9K GitHub stars and 3.4K forks on GitHub has more adoption than Hoodie with 3.51K GitHub stars and 314 GitHub forks.
What is CakePHP?
What is Hoodie?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using CakePHP?
What are the cons of using Hoodie?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Hoodie?
Sign up to get full access to all the tool integrationsMake informed product decisions
The main pro of CakePHP is "bake" functionality and use of conventions, which, if you follow them and buy into them you can really create some complex, large applications quite fast. Faster than any other PHP framework I've ever used, and I've tried all the popular ones.
However, my issues with Cake are as follows:
The ORM is slow. Slower than many of the alternatives. It's queries sometimes do strange things like querying 2 tables separately instead of using a join and I've often faced memory issues stemming from the ORM.
The code conventions, while since 3 they have adopted PSR-2 are still a long way to go to being as compliant with the many PSRs as say, Laravel and Symfony. For example the controllers have an "initialize" method which is doing what you would/should do in __construct. Bugs me.
The template layer needs to be Twig and not the ctp one. This is where the conventions fall apart and I've seen controller code, and tonnes of php logic in views because ctp offers nothing useful, unlike twig or blade templates which are very clean in comparison.
That said I work on a project with hundreds of models and controllers and it holds up really well. I couldn't imagine the same application in Laravel or Symfony. It would be a mess.
CakePhp has is own Comunity and its very coprative they helpd me lot wen i wind no way to resolve a problem then i go for googling and Stack OverFlow but when we could not find any answer then we have to just post and shere issue with CakePhp Community and get answer Shortly
CakePHP is used because it is a very feature-complete, battle-tested rapid development framework. This saves us months of development time because the API's do most of the work. There is also an extensive plugin and community built around this platform.
CakePHP is one of the most mature and developed PHP Frameworks available, it brings order to Chaos and the core team are a decent bunch of people who really care about the project