The Problem with Dependency Injection Frameworks

Re:The Problem with Dependency Injection Frameworks by justesjc on Sunday January 08, 2023 @03:07PM (#34302555)

Are you evaluating the points made by James from your context and limiting your understanding? If you work for a company where software is not a differentiator, but a cost to doing business, then using frameworks, DI or not, is probably the right thing to do. But if your code is a core part of the business, you probably don't want to give control to some third party that may screw you.

All successful companies that I have worked for where the code is core to the business, rolled most of their own software (NPM for the web aside). Long term you need that control, understanding and speed of change if required.

[ Parent | on HN ]

Re:The Problem with Dependency Injection Frameworks by rektide on Sunday January 08, 2023 @03:35PM (#34302813)

What major upheaval examples should we fear? DI frameworks seem quite reloable, trustworthy, & consistent. I cant think of any examples of a community being burned by trusting their framework. I cant think of any cases or blogs where someone has been left up a creek, has ended up hard clashing with their framework

I dont see what justifies this fear, uncertainty, and doubt.

[ Parent | on HN ]

Re:The Problem with Dependency Injection Frameworks by oezi on Sunday January 08, 2023 @06:08PM (#34304363)

Yes, I evaluate it from the perspective of developing enterprise software where I need to designate extension points for a fluid number of team members. Only using CI can I balance the flexibility of offering the interfaces people need with the oversight needed.

Also just develop your own DI if you consider it business critical but not yet commodity (you don't do your own logging/crypto/math libs, right?).

[ Parent | on HN ]