Re:One Year After Switching from Java to Go: Our Experiences
by bcrosby95 on Wednesday February 19, 2025 @12:29AM
(#43098889)
DI frameworks save you from writing trivial code, and it masks dependency insanity. This is why I don't use it even in Java. If the codebase gets to the point where a DI framework is really useful then you've fucked yourself over.
[ Parent
| on HN ]
Re:One Year After Switching from Java to Go: Our Experiences
by unscaled on Wednesday February 19, 2025 @07:18AM
(#43101250)
To be fair, traditional Java EE apps often required a DI framework, because you couldn't control the main entry point of the program, and the entry point to your code was a class with a default no-argument constructor.
This is still insanity, but the insanity comes from Java EE rather than the apps themselves.