I am new to the DI concept, but I used it to some extent in my projects - mainly by "blowing" interfaces into constructors and creating factories of my specific classes. Well, this is not configuration based, but it never needs to be.
I started learning DI structures like Spring.NET and Castle Windsor, and came across this blog from Ayende.
What I got from this
A) The DI structures are awesome, but B) This means we don’t have to worry about how our system is designed in terms of dependencies.
For me, I'm used to thinking a lot about how to freely connect my system, but at the same time have some control over dependencies.
I'm a little afraid to lose this control, and it's just free for everyone. ClassA requires ClassB = no problem, just ask and you will get! Hmmm.
Or is this just the point, and this is the future, and I should just go with it?
Thoughts?
source
share