Similar to the other frameworks, CodeIgniter was chosen due to its community and popularity. It has much of the same aspects of the other frameworks we evaluated, except .Net which obviously doesn't use PHP. CakePHP has a CakeBake function that we wish we had with CodeIgniter, …
CodeIgniter has a very small footprint. The source code is very small sized. Setting up a project is very easy. Follows MVC pattern. Consumes low memory and CPU. Well documented. Has a built-in forum for users to discuss and get the solution for issues. Periodically updates …
We chose CodeIgniter because although it has a steep learning curve, ultimately it suited our needs better in terms of how well it scales for larger applications.
In my experience, I tinkered with Zend and Cake initially before CodeIgniter. I recall getting stuck multiple occasions with Zend and Cake when I first started learning the MVC architecture. When I found CodeIgniter, the experience was different and it was much easier to learn. …
Laravel is the de facto upgrade path for any and all web developers coming from any version of CodeIgniter. However, Laravel brings a level of complexity that can be intimidating to new developers or wasteful to experienced developers with simple requirements.