Dependency injection is so much worse. Oh, hey, where'd this value come from? Giant blob of opaque reflection code.
It can be used in bad ways, but if it's used in the right way you should never have the situation you just described.
Same could be said of a global. There's a time and a place for each.
One thing I'll say is I don't remember us needing a team of senior+ devs to handle web app back in the day...
I'm not exactly sure what you mean. Doesn't all dependency injection work the way I described?
Without being familiar with the framework, you can't trace your way from the class getting injected into to the configuration, even if you're experienced with the language.
I don't think so. When I've seen it done it's usually not been random values injected (except when those values are secret keys which should absolutely not be stored in code to begin with), it's usually injecting a service. Another class, usually with a name that makes it easy to trace down. Like if you're building an OrderService, that might take as a dependency an IProductService, which would have injected into it the class ProductService (personally, I don't like the Hungarian notation that C# uses, but it's a convention and my preference for sticking to strong conventions for the sake of consistency outweighs my distaste for Hungarian notation). That's easy to find, and in fact your IDE can probably take you straight to it from the OrderService's constructor.
I'm using value in the loosest sense, like how all objects are values.
So now if you have three implementations of IProductService, how do you know which one is configured?
It's easy to imagine a hypothetical way that could lead to problems. But in all the code I've worked with, either that scenario is avoided entirely, or other context makes it absolutely clear which IProductService is being used.
Dependency injection is so much worse. Oh, hey, where'd this value come from? Giant blob of opaque reflection code.
It can be used in bad ways, but if it's used in the right way you should never have the situation you just described.
Same could be said of a global. There's a time and a place for each.
One thing I'll say is I don't remember us needing a team of senior+ devs to handle web app back in the day...
I'm not exactly sure what you mean. Doesn't all dependency injection work the way I described?
Without being familiar with the framework, you can't trace your way from the class getting injected into to the configuration, even if you're experienced with the language.
I don't think so. When I've seen it done it's usually not been random values injected (except when those values are secret keys which should absolutely not be stored in code to begin with), it's usually injecting a service. Another class, usually with a name that makes it easy to trace down. Like if you're building an
OrderService, that might take as a dependency anIProductService, which would have injected into it the classProductService(personally, I don't like the Hungarian notation that C# uses, but it's a convention and my preference for sticking to strong conventions for the sake of consistency outweighs my distaste for Hungarian notation). That's easy to find, and in fact your IDE can probably take you straight to it from theOrderService's constructor.I'm using value in the loosest sense, like how all objects are values.
So now if you have three implementations of
IProductService, how do you know which one is configured?It's easy to imagine a hypothetical way that could lead to problems. But in all the code I've worked with, either that scenario is avoided entirely, or other context makes it absolutely clear which
IProductServiceis being used.