Definitely a preference thing- no doubt. But thank you for responding anyway. (As a clarification, in case it's needed: I obviously didn't LOVE it when I had

Definitely a preference thing- no doubt. But thank you for responding anyway. (As a clarification, in case it's needed: I obviously didn't LOVE it when I had to update 20 ctors after changing a somewhat fundamental "service" to need a new dep. My point was that, even as painful as that was, it wasn't that bad and it's usually much less bad than that.) I guess the (philosophical) difference comes to this statement: > The intermediate classes that _do technically depend on FooService because BarService does_ - the intermediate classes don't care! I can definitely understand what you're saying there, but it's interesting to me that I don't see it that way. I think I'm just less pragmatic and more... "academic" (?) about how I read and understand my own code. If X depends on Y and Y depends on Z, I'm comfortable with X explicitly depending on Z because I imagine "inlining" Y's functionality in X. Either that or you turn Y into an interface and then X only depends on IY. But, my brain just likes the explicit continuity I guess. Cheers!