The Dark side of Dependency Injection

I have been thinking about dependency injection from time to time. I have long suspect that the issue of couplings being adressed by DI framework must have given rise to some problems elsewhere. There is no free lunch. Remember whack-a-mole syndrome?. Like a nuclear reactor with almost indefinite energy production and  yet generate those radioactive waste as the consequence of operating one. The following article "This dependency injection madness must end!" highlight problems created by  using DI framework. Notable quote from above article:

First, understanding which dependency is actually used (and why!) can require a lot of brain power: It will require you to consider all possible configurations when you look at a dependency and it will not work well with the normal code navigation functionality of your IDE. Second, the configuration will tend to deteriorate: When you no longer use a dependency, will you check whether you can remove it, or will you just leave it there to be safe?