|
|
|
|
|
|
by shellac
4339 days ago
|
|
|
On larger code bases it can help a lot. You get to a point where you need that config object over in some random function and you start weaving it through constructors. At which point a simple DI system really appeals. DI code also tends to be more pleasant to test in my experience since it promotes loose coupling. |
|
|
http://commandcenter.blogspot.com/2014/01/self-referential-f...
And you should probably avoid situations where you suddenly need config objects in 'random places'. This could be a symptom of chaotic API design. But then again, whatever works for you.