Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Oktokolo89618dWould have never expect something like an injection framework to exist.
Dependency injection is like security - if the code isn't build with it in mind, you can't just get dependency injection working by burying it under more code.
But if you refactor the code anyways - what does the framework do?
@Oktokolo by refactoring , i meant if i have to just include the concepts of DI in my already deployed app. that would just require shifting a few things to caller classes and would count to 5-10% of changes and 2-3 hours of work.
But this framework is a mamoth, providing all different ways for injecting different types of dependencies : the one which whose constructor is accessible to us, the one who constructor isn't accessible to us, the dependencies which are instances of interfaces, using factory vs using builder for providing dependency... it has a lot of stuff.
well maybe its good in the long run, but its learning curve is steep and it complicates a lot of stuff