Why I stopped using Spring

Re:Why I stopped using Spring by ivan_gammel on Wednesday December 25, 2013 @01:57PM (#6963837)

In good design the intent is clearly defined in interface on which you depend. If the code has side effects, if it does something not specified by interface, if it has more than one role, this code needs to be fixed and it is not a problem with DI. It's a problem with your design.

As I already said, you always need to wire your objects. You do it, possibly, without realizing it, but you still do it. If you reject the idea of DI just because the code is bad and DI is "Not Invented Here", you will not do the wiring better. Writting custom DI is hard, and it's very likely that you will end with unmaintainable nightmare that needs to be rewritten completely. For 15 years I've seen this nightmare too much and never seen the successful projects with custom DI.

[ Parent | on HN ]

Re:Why I stopped using Spring by sitkack on Wednesday December 25, 2013 @05:31PM (#6964520)

So is DI a result of incomplete language design? Should the concept of DI be baked in?

[ Parent | on HN ]

Re:Why I stopped using Spring by ivan_gammel on Thursday December 26, 2013 @04:17AM (#6965724)

For enterprise software, for large projects, probably, yes. Together with more advanced reflection (I imagine MOF/EMF as a native part of Java) to allow meta-programming and smarter code generation.

[ Parent | on HN ]