Pros and cons of Cakephp versus Laravel
Dear Cakephp gurus, I have used cakephp in a past project (simple one) and I would like to continue using cakephp in a new project. There are some voices which advocate using Laravel which is an up-and-coming php framework. For experienced programmers who know something about both frameworks, could you tell me what are the pros and cons? Since I use cakephp before, here are my comments about cakephp; Pros - It uses convention over configuration I like this because I am forgetful. If the framework uses configuration over convention, I may miss out things to configure when things are changed or added to the code. Cons - It does quite a bit of magic in the background(can be good or bad) and loses flexibility in the process. If the programmer wants to do special things, he may have to fight cakephp. -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups CakePHP group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/groups/opt_out.
Re: Pros and cons of Cakephp versus Laravel
I've not had experience with Laravel, but with regards to the magic being a con, specifically when it comes to the convention of models, table names and controllers, I've had plenty of experience with using legacy databases that don't conform to the convention, and have still been able to use them, without changing the database to suit. That flexibility one of the reasons I use CakePHP. You can override $name on the controller, and use a controller name that doesn't conform to the convention. You can override $useTable [http://book.cakephp.org/2.0/en/models/model-attributes.html#usetable] on the model, to map to a table that doesn't use the plural convention. And you can use $useTable to suppress mapping to a table altogether (for implementing web services via the model). The only time I've had to fight CakePHP is when I want to extend the FormHelper to add additional types, or override existing types for alternate output and convenience. However, that doesn't happen very often. With a minor modification to the core (index.php), I've never had success in integrating CakePHP Sessions into legacy applications so I can gradually migrate and introduce new functionality using CakePHP to the legacy application. If there are specific cases of magic that you're concerned with, let us know, and someone could probably tell you if what you're wanting to do would be a problem or not. Regards Reuben Helms On Monday, 20 January 2014 12:17:27 UTC+10, Sam wrote: Dear Cakephp gurus, I have used cakephp in a past project (simple one) and I would like to continue using cakephp in a new project. There are some voices which advocate using Laravel which is an up-and-coming php framework. For experienced programmers who know something about both frameworks, could you tell me what are the pros and cons? Since I use cakephp before, here are my comments about cakephp; Pros - It uses convention over configuration I like this because I am forgetful. If the framework uses configuration over convention, I may miss out things to configure when things are changed or added to the code. Cons - It does quite a bit of magic in the background(can be good or bad) and loses flexibility in the process. If the programmer wants to do special things, he may have to fight cakephp. -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups CakePHP group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/groups/opt_out.
Re: Pros and cons of Cakephp versus Laravel
The thing that I like more about cakephp is it is simple for a beginner programmer like me, before I had tried many frameworks but cakephp I was the only that made sense for me. (I'm not a programmer genius) 2 months ago I tried laravel and it was simple to understand like cakephp plus had many features never seen before in PHP like the ORM system. Now I'm using laravel in all my new projects. On Sunday, January 19, 2014 7:17:27 PM UTC-7, Sam wrote: Dear Cakephp gurus, I have used cakephp in a past project (simple one) and I would like to continue using cakephp in a new project. There are some voices which advocate using Laravel which is an up-and-coming php framework. For experienced programmers who know something about both frameworks, could you tell me what are the pros and cons? Since I use cakephp before, here are my comments about cakephp; Pros - It uses convention over configuration I like this because I am forgetful. If the framework uses configuration over convention, I may miss out things to configure when things are changed or added to the code. Cons - It does quite a bit of magic in the background(can be good or bad) and loses flexibility in the process. If the programmer wants to do special things, he may have to fight cakephp. -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups CakePHP group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/groups/opt_out.
Re: Pros and cons of Cakephp versus Laravel
I just had a quick gander at the doco. Whilst ORMs aren't never seen before features in PHP (looking at you, Doctrine), it certainly seems like Laravel is at a place where CakePHP 3 is going to take existing CakePHP users. PHP 5.4 using namespaces, location services implemented at static functions on the model (CakePHP 3 will split the 2.x Model into Table/Entity) and a fluent API. The big difference might be that Laravel is built using Symphony components, so it's a framework on a framework, where as CakePHP doesn't depend on other PHP components, other than composer (as does Laravel). Had Laravel existed in late 2008 when I went looking for a PHP MVC framework that I could integrate with legacy applications, then I might have easily gone with Laravel instead. Although, from memory, Symphony was a little bit all or nothing back then, and I'm not sure that any other framework built on top of it would have been any more flexible. On Mon, Jan 20, 2014 at 3:40 PM, Cesar Felipe cesarfel...@gmail.com wrote: The thing that I like more about cakephp is it is simple for a beginner programmer like me, before I had tried many frameworks but cakephp I was the only that made sense for me. (I'm not a programmer genius) 2 months ago I tried laravel and it was simple to understand like cakephp plus had many features never seen before in PHP like the ORM system. Now I'm using laravel in all my new projects. On Sunday, January 19, 2014 7:17:27 PM UTC-7, Sam wrote: Dear Cakephp gurus, I have used cakephp in a past project (simple one) and I would like to continue using cakephp in a new project. There are some voices which advocate using Laravel which is an up-and-coming php framework. For experienced programmers who know something about both frameworks, could you tell me what are the pros and cons? Since I use cakephp before, here are my comments about cakephp; Pros - It uses convention over configuration I like this because I am forgetful. If the framework uses configuration over convention, I may miss out things to configure when things are changed or added to the code. Cons - It does quite a bit of magic in the background(can be good or bad) and loses flexibility in the process. If the programmer wants to do special things, he may have to fight cakephp. -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to a topic in the Google Groups CakePHP group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/cake-php/KvA7AYFLx6g/unsubscribe. To unsubscribe from this group and all its topics, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/groups/opt_out. -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups CakePHP group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/groups/opt_out.
