Breaking Up with IoC Containers
justinbozonier.posterous.com
justinbozonier.posterous.com
I'm biased (I wrote a DI framework for .NET), but I don't really understand what people think they're gaining by avoiding the use of a container. The complexity of dependency wiring increases geometrically with the size of your application, and I personally would like as much of that complexity hidden as possible.
On static languages, using a dynamic language DSL to configure the container will usually do wonders, while losing refactoring support (for instance, Spring plugin for Eclipse will be aware of all rename methods and rename classes, as long as you use the xml for configuration).
I say all this as a relative newcomer to IoC containers but the work I have done on large applications with both Castle Windsor and Ninject has me currently in the camp that a container can make dependency management a great deal easier with the tradeoff of making it slightly harder for new developers (especially those with zero DI/IoC experience) to figure out what's going on. IoC containers make large, complex apps much more pleasant to work on, IMHO.
Some applications don't require this sort of runtime flexibility and they have dependencies that are not likely to change in future versions, in which case it may be fine (even preferable) to dump all the dependencies on the user.