So a friend running a small business asked me to develop a website for him. Looking for a light-weight php framework, I decided to do it in codeigniter. But going through the documentation, I noticed it doesn’t come with a DI container out of the box but rather provides a service class for creating your objects . Although the service class resolves and provides all the dependencies the class will need, I still don’t like fact that you will manually call the service class from inside the controller. Do DI containers affect application performance? If not, why is codeigniter doing it differently.

It won't affect anything

silento:
It won't affect anything

I quess they just want to do something different then.

chukwuebuka65:
So a friend running a small business asked me to develop a website for him. Looking for a light-weight php framework, I decided to do it in codeigniter. But going through the documentation, I noticed it doesn’t come with a DI container out of the box but rather provides a service class for creating your objects . Although the service class resolves and provides all the dependencies the class will need, I still don’t like fact that you will manually call the service class from inside the controller. Do DI containers affect application performance? If not, why is codeigniter doing it differently.

DI is more of a design pattern.

qtguru:

DI is more of a design pattern.

Ok.