2 ms·
> Which IoC? Well, I have seen some heat specifically against the habit popular on Java and C# of passing dependencies into factories and getting classes with
by marcosdumay 3y ago
> Which IoC?
Well, I have seen some heat specifically against the habit popular on Java and C# of passing dependencies into factories and getting classes with completely different interfaces as a result.
But you are correct, IoC is a very generic name that can cover even passing lambdas to a map function.
Anyway, the problem with deviating from the single source of truth plaintext is that when other sources of truth have bugs, you are usually forever unable to fix them¹. This is because when people create tools that affect the program behavior independently of your source, they inevitably make them stateful. A stateless tool could in theory not have this problem, but then, developers are annoyingly good into reducing your stateless tool "configuration script" into normal code and using that instead.
1 - There are many programing environments where tools affect the program behavior. Those are usually aimed into novices and non-programmers, because programmers with any experience are quick to reject them. A very common theme on those environments is that error that keeps happening despite everything being correct, and can only be solved by throwing your work away and doing everything again exactly the same way from scratch.
- rewmie 3y ago> Well, I have seen some heat specifically against the habit popular on Java and C# of passing dependencies into factories and getting classes with completely different interfaces as a result. In other words, you saw a bug in a software implementation. What leads you to look at a bug and from that lay broad and overreaching personal claims about fundamental design patterns?