I've been using IntelliJ IDEA so long that I probably take it for granted now, but I don't remember the last time I had issues navigating a codebase that used DI. While I tend to dislike magic, there are plenty of mature DI frameworks that "just work" and I'm totally isolated from any complexity. And, ultimately, what tends to emerge from codebases that don't use DI is either a) extreme coupling or b) some homegrown quasi-DI mechanism.
I've also had zero issues with DI perf, if only because the kinds of applications that leverage DI are IO bound, not CPU bound.
bkv3 karma
I've been using IntelliJ IDEA so long that I probably take it for granted now, but I don't remember the last time I had issues navigating a codebase that used DI. While I tend to dislike magic, there are plenty of mature DI frameworks that "just work" and I'm totally isolated from any complexity. And, ultimately, what tends to emerge from codebases that don't use DI is either a) extreme coupling or b) some homegrown quasi-DI mechanism.
I've also had zero issues with DI perf, if only because the kinds of applications that leverage DI are IO bound, not CPU bound.
View HistoryShare Link