Are you pro DI as in "Dependency Injection", or pro DI as in "Dependency Inversion Principle"?
DIP is a good way to build software. When injecting dependencies becomes so complex you need a framework or need a separate concept of DI (sans P) then I think something has gone wrong, incidental complexity has won.
I mean the original statemement from the perspective that only certain languages/environments (Java, etc.) propose DI as a solution. E.g. in my current language of choice, C++, DI is nowhere to be found.
I don't think DI itself really causes any problems, the solutions designed to save you from a little bit of boilerplate code, cause the problems.