4 ms·
Some of us working in hybrid OO-FP languages or strictly FP languages might argue against IoC. I have seen and been exposed to code bases while beautifully writ
by wheaties 14y ago
Some of us working in hybrid OO-FP languages or strictly FP languages might argue against IoC. I have seen and been exposed to code bases while beautifully written are completely untraceable in cause-effect debugging. Which combination causes the error? Which config was that environment set to? Let me try to divine the structure...
- grdvnl 14y agoAgreed. There is a fine line on how much of this should be used. Teams can spend cycles trying to design everything based on IoC which might be overkill. All rules regarding keeping things simple should also apply to IoC.
- narag 14y agoI've always worked with OO, not FP. I dislike IoC for the same reasons. Also it's anti-KISS and debilitates encapsulation. The worst effect of this kind of doing things is the image of programming that it shows to beginners. Programming well has nothing to do with that, really.
- Zimahl 14y agoAgreed, I think IoC is dramatically overrated along with AoP. There are places it can be useful but it can get so complicated so quickly it actually hinders the upkeep of the application.