Looks like we reached maximum thread depth so replying here. I agree, the side-effectful choices are either a global, some DI container, or just passing it dow

Looks like we reached maximum thread depth so replying here. I agree, the side-effectful choices are either a global, some DI container, or just passing it down. For loggers, I think global lookup from some (pluggable) logging library is justified because logging is probably the most ubiquitous cross-cutting concern ever. For pretty much everything else, I think passing as a parameter is actually the best option. It's explicit and simple, and you don't even need to explicitly pass it around _that_ much if you store it in a field of a class that plays the role of a module. Most uses of the dependency will be in non-static methods, lambdas, or inner classes. I dislike Reader because it's similar to a DI container (or a global) in that it's more work to figure out, for a given call site, what the last value written to it was. With parameters, you just climb the call chain.