Need advice about which tool to choose?Ask the StackShare community!
CakePHP vs Kohana: What are the differences?
CakePHP: 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; Kohana: An elegant HMVC PHP5 framework. Kohana is an elegant, open source, and object oriented HMVC framework built using PHP5, by a team of volunteers. It aims to be swift, secure, and small.
CakePHP and Kohana can be primarily classified as "Frameworks (Full Stack)" tools.
"Open source" is the primary reason why developers consider CakePHP over the competitors, whereas "Open source" was stated as the key factor in picking Kohana.
CakePHP and Kohana are both open source tools. CakePHP with 7.9K GitHub stars and 3.4K forks on GitHub appears to be more popular than Kohana with 1.61K GitHub stars and 464 GitHub forks.
According to the StackShare community, CakePHP has a broader approval, being mentioned in 66 company stacks & 29 developers stacks; compared to Kohana, which is listed in 3 company stacks and 3 developer stacks.
What is CakePHP?
What is Kohana?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose CakePHP?
Why do developers choose Kohana?
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 Kohana?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Kohana?
Sign up to get full access to all the tool integrationsMake informed product decisions
CakePHPThe 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.
CakePHPCakePhp 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
CakePHPCakePHP 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.
CakePHPCakePHP 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
CakePHPAdmin interface for users.
CakePHPThe best FW