CodeIgniter vs Laravel

February 22, 2013

Hi,

So a bunch of CodeIgniter nerds/contributors decided to build a new framework because things about CodeIgniter didn’t sit too well with them … tell me something new.

Don’t get me wrong, I am not putting down the Laravel crew for what they did, I just wanted to point out this happens all the time.

So what’s the point of this Friday afternoon blog post?

Well, my right-hand-nerd started to look into Laravel just a few days ago, and he found that it did indeed have some nice advantages over CodeIgniter out of the box:

  • Integrated auth library.
  • Easy layout/templating.
  • Bundles – bundles are like external modules created by third party developers.

We’ve created a few projects at killerSites using CodeIgniter because it was the preference of my left-hand-nerd at the time (another fine nerd programmer) – and he knew CodeIgniter well. In moving to CodeIgniter, I actually broke my rule of not switching frameworks … up until then, we used the Zend Framework. But the key point for me was we had CodeIgniter skills already and so we didn’t have to learn something new on the fly – thus I broke my rule.

It’s a good thing to learn new frameworks

Learning a new PHP framework has one huge advantage: it makes you a better programmer.

Why?

Because you can compare frameworks off each other. You will be able to see how different design strategies work, and judge for yourself what works best.

In the end, you may find the new Framework only does some things better and it may even do other things worse than the old framework (happens a lot) … Whatever the case, it’s probably a bad idea to learn something new when you have deadlines looming.

… And that’s what my right-hand-nerd discovered, when he thought of using Laravel for a new project he was starting on. So after a few hours of digging into Laravel (and really digging it,) he opted to go back to what he knew, CodeIgniter. At least for now.

Check out CodeIgniter

Check out Laravel

Stefan Mischook
killerPHP.com

4 Responses

  1. andy brookes Author February 23, 2013 at 8:18 am

    I had a look recently at php frame works such as Yii, codeignitor ,symfony, seagullproject and so on; what led me to have a look at these frameworks was the impression that the software can lever or enhance my php coding skills to build web sites and so on.

    At the stage i’m (greenhorn) I did manage to download Yii into a subdirectory of htdocs of the “php ,MySQl all in one XAMPP” and did see the starter page of Yii.

    However I found myself out of my depth and considered at this stage looking at slicing in pre-written classes instead, to help give extra functionality and also just keep playing with php code until I get better.

    So I guess for frame works its probably a case of re-visiting if & when I get out of a greenhorn phase.

    I think there is some merit though of maybe an intro tutorial on frameworks in a similar vein to the excellent into to php objects at: http://www.killerphp.com/tutorials/object-oriented-php/php-objects-page-1.php

  2. Stefan Mischook Author February 23, 2013 at 12:04 pm

    Hi,

    I will think about your suggestion. Thanks for the kind words.

    Basically, frameworks provide a structure for your applications and code libraries for common task like validating user input, connecting to databases and displaying database results in grids on web pages etc …

    The big advantage of using a framework is that you don’t have to write all this nuts-&-blots code. Besides, you can expect code from frameworks to be highly vetted – less chance of bugs.

    Stef

  3. Stefan Mischook Author November 21, 2013 at 12:28 pm

    I’ve reopened comments given the popularity of this article.

    Stef

  4. Stefan Mischook Author November 21, 2013 at 12:30 pm

    UPDATE:

    At this time, I would strongly recommend Laravel over CodeIgniter … we simply feel it is a superior framework in several ways.

    Stefan

To Top