My favourite PHP Framework has just been updated and I am delighted to say it is as fast as ever - even with the included debugging scripts.
Latest version only works on PHP7 and appears to be following the latest trend of other considered platforms. For the past month I have been playing with the GitHub Pre-release version and it looks as though upgrading from previous versions will not be an easy task Previous upgrades were usually very simple and usually required a single path change to index.php -> $system_directory = '../system'; Complete versions were usually about 2.6 MB including the comprehensive User-Guide!
For those not familiar with this PHP Framework, it was first introduced by EllisLab way back in February 28, 2006 - now over ten year ago. Further details from Wiki CodeIgniter
I just finished building a custom CRM for a client using CodeIgniter 3 (with plans for future additional features). Would it be worth my while upgrading to CodeIgniter 4 or should I just leave it and make the switch with my next project?
What do you think are the biggest plusses of this new version?
That’s not the case, and certainly not a very productive comment for this thread. I also use Laravel, but for this project CodeIgniter was, in my opinion, the best man for the job.
Okay, my comment is no longer relevant, because you just edited your post. But try not to be insulting, please.
I’ve used plenty of other systems and have been using CodeIgnitor now for about 6 months. The entire thing is trash. I don’t want anything else to do with it. Neither should anyone else. The project is just grasping at straws at this point. Its no wonder people move onto node and we honestly have people pushing such out-dated and poorly built crap as Code Ignitor in php.
Just repeating your insults doesn’t help anyone @oddz. We get that you don’t like Codeignitor but other than it being your personal opinion, do you have any objective reasons for your comments?
CodeIgniter 3.X will be supported for a considerable time and as mentioned upgrading an existing project will require a lot of work. Will your client pay for a back-end upgrade which will not affect the rendered site?
I also believe it will be a couple of months before the final CI4 release version will be available. Previously detailed instructions were supplied on upgrade procedures.
Biggest plus is that PHP 7 is mandatory and no doubt will utilise all the latest features.
CodeIgniter’s website forum has more details and is frequently updated.
Comparing the two like that is a drastic over simplification. Up until this new version CodeIgniter didn’t even use namespaces or dependency management.
When it takes such small project so long to implement basic modern design patterns I see that as a red flag. The entire thing is holding on by its finger tips. Especially with the amount of people who have started moving to other technologies like node.js. To little to late. Code Igniter and Cake are relics of the past as far as I’m concerned.
Have you even looked at the code in Code Igniter. Its basically a bunch of procedural spaghetti code that uses classes as namespaces. I’m sure the code in 4 is better but still… not a project to be impressed by when compared to Laravel and Symfony’s architecture.
Not to mention Code igniter tends to have a lot of custom code for features that would be better delegated to well known libraries. Libraries that have considerably more community, flexibility, documentation, and well-thought architecture.
Code Igniter is a very selfish, and stubborn framework. That isn’t something people should support.
Reviewing this version of Code Igniter the project is basically the same thing with namespaces and auto-loading. Nothing has really changed. Still a bunch of custom, selfish, stubborn custom code. Still basically a simple MVC wrapper with not much more to offer besides writing a lot of boilerplate code and functionality yourself.
Honestly I am a little surprised that it only works on PHP 7, considering CodeIgniter 3 still supports PHP 5.2 this is a huge leap. CodeIgniter also had history of resisting the latest industry trend, as it was among the few opposers of the Go PHP5 movement back in the older days.
Previous upgrades were usually very simple and usually required a single path change to 