True D.I. vs service locator.

From expiramenting with a lot of frameworks, to building my own, I've found at the core of the whole framework lies a decision that makes a huge difference in the ease of use. I'm talking about dependence injection vs a service locator, and the specific implementation. This is a make or break feature. For instance, I think we can agree that CI's loading of resources is about as simple as it gets. A person who uses CodeIgniter is not going to step right into Symfony 2 dependency injection and feel at home. There is a DI container that is called Pimple which is extremely easy to use, but I've seen where some consider this a service locator. I truly think Pimple should be looked at by the CI4 planners, because it is just so easy to use. I built a framework using it and used some CI classes, and it was very simple, and still has a CI feel to it.

I'm not in a position to open up my repo to the public, but wouldn't mind sharing what I've done with some of the higher ups who will be making the decisions. If anything it might help show a complete implementation of what CI4 could be, and might help with the decision making process.

So, needless to say, I'm interested to hear what other people think about this.

Expert Website Development - Temecula, CA
Community Auth For CodeIgniter 3