CI vrs Laravel, god this is a horse that has been beaten to death, then beaten to death again, and again, and again, and so on.
things i do not like about laravel.
Routing - overly complicated and bloated. the old say: Keep It Simple Stupid applies here.
Complete Re Writers for every version after version 3. WTF is wrong with these people? In CI the old say of: If it aint broke don't fix it applies, in Laravel it is if it aint broke fix it anyway. a dumb and stupid waste of manpower.
and that is just the tip of the iceberg. I will not go into all of it, because it is too much to type.
CI Does not support Composer easily - simple answer: BIG F*(&^*&^ Deal. I would rather create my own stuff anyway. That way if it breaks, it is my fault because it is MY code. Not some other jackasses code whom only thinks he knows what he/she is doing.
CI does not use Namespacing - again BIG F*(&^*&^ Deal. However Namespacing would be cool as i came from C++ and C# ect ... namespacing is natural to me. But i am not going to cry foul because i do not have it.
Laravel has some cool stuff in it, yes. But Laravel is one of those frameworks that tries to do it all for you, thinking your a complete idiot and need to be told what to do. CodeIgniter does not.
Someone said that Laravel allows you to do certain things that CI does not. How can a programmer say that? Anything you can do in other frameworks you can do in CodeIgniter. It just comes down to the drive to do it.
If i develop an app on Laravel, by the time i release it and get to my first update patch the version of Laravel has changed and all that effort i put into my app is now complete F&^%&*^% useless because that version of Laravel is no longer supported. And if you try to keep using that version your basically shunned.
Where as in CI if you create an app in say version 1.7.2 you can easily migrate to the newest release of CI with little effort and most if not all of your code is still good.
Some people here say the session in CI is broken and always has been. I can agree that it needs some updating but i would never say that it has always been broken. I must be alone here when i say i have never had an issue with CI's Session. Well not until recently when i moved from 2.2 to 3.0. But work on the session library is being done so happy day
at the end of the day it boils down to apples and oranges. Both are really good, but an apple is easier to eat, pull it out of fridge, rince and eat. Oranges you have to peal these bastards just to get to the good stuff, or pull out a knife and cut it apart.
"I reject your reality and substitute my own" - Adam Savage, M5 Inc.
