Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 4
    +1 You hit a nerve. I don't like needing reflection or a DI/IoC framework to instantiate a class. It's like driving to Rome to get to Paris from Amsterdam. Mind you I love DI. Just not sure about the frameworks. Commented Oct 25, 2015 at 11:09
  • 1
    Great arguments. It verbalizes a lot of the thoughts I had myself but I am happy to see others feeling the same way. As amazing as I used to find field injection, I think I loved it so much simply because it was "easier". I find constructor injection so much clearer now. Commented Oct 25, 2015 at 15:07
  • In one of the projects, I had all classes being autowired by field injection. I changed them all to constructor injection. The application was taking more time or equal time to start. So I would say that there is no performance gain for constructor DI over field DI. Commented Jun 9, 2020 at 14:21
  • You would need to create a micro-benchmark that does only constructor injections and field injections in order to acurately state something like that. Commented Jun 23, 2020 at 19:44