CodeIgniter VS Slim Framework

CodeIgniter is an open-source PHP framework with 18k+ stars and 7.8K forks on GitHub. It follows the Model-View-Controller (MVC) architecture and provides a structured way to create and organize code. It provides a set of libraries and an intuitive interface to accelerate PHP web app development.

Over the years I have tried different frameworks, mostly in PHP, like Code Igniter (2010), ProcessWire (2014) and Laravel (2015).

CodeIgniter is an open-source php web application framework created by EllisLab Inc and it is now a project of British Columbia Institute of Technology. The framework implements a modified version of the Model-View-Controller design pattern. It is praised for its performance and the quality of its documentation. It's currently licensed under the MIT License, although the previous version was released under the Open Software License ("OSL") v. 3.0.

Look at the issues and pull requests. It doesn’t support php 8 properly, hence why I call it outdated https://github.com/bcit-ci/CodeIgniter/issues

CodeIgniter

It's been a long time since I wrote any PHP in anger but back when I did, I got a ton of mileage out of CodeIgniter (https://codeigniter.com/). It looks like it's still around and being actively maintained. I can quite clearly remember a number of projects that went from being just an idea to 90% functional in the span of an evening.

I write Python almost exclusively now, but still pine for something like CodeIgniter. Flask is nice because it lets you bolt on whatever you want, but you spend a lot of time choosing, prototyping, and often discarding libraries. Django does a lot of heavy lifting but has (IMO) a very steep learning curve. There doesn't seem to be anything (or at least anything I've liked) in between.

Slim is a micro PHP framework used for web development with 11.7k stars and 2k forks on GitHub. It has a simple and intuitive API development process. It is a micro-framework, meaning you only get a minimum of support for HTTP requests and forwarding requests to appropriate controllers. So the question is, why should you choose a micro-framework? Because it offers you flexibility and high extensibility.

Slim is very lightweight and has a similar API to Express https://github.com/slimphp/Slim

Yes, I've opened a ticket with Slim. I also saw it in a non-slim file (Pimple) so I don't think it is a Slim issue.https://github.com/slimphp/Slim/issues/2160

Sounds like part of Slim's RoutingResults. Which then is pretty much:

Switched from Python to PHP and now using Slim. Very happy with the move so far.

At my day job we needed to develop an API and I've never really tried to build one using vanilla PHP, but instead used frameworks such as CodeIgniter or Slim or just a simple file that would mimic the functionality of an API but not be a proper one. Also we had a requirement that we needed to have full control over the code so we were not supposed to use any of the pre built solutions because of that requirement.