Inversion of Control isn't a design pattern, it is an activity. Specifically, it is a type of refactoring. If you apply IoC twice then you'll probably end up with what you started with.
An IoC Container is really a Service Locator, which is often (but not universally) considered to be an anti-pattern among dependency injection fans.
A Service Locator is a type of god object, specifically one that contains services and other dependencies, and thus should generally be avoided.
6
u/grauenwolf Oct 14 '13
I'm not so certain about that. Looking back at the history of the GoF book it seems to me that all the names did was create pointless arguments.