Though I agree with what the author writes I'm a bit disappointed that only that's done is tear down this concept but not really provide good alternatives or examples of how it (c|sh)ould be done instead. Just passing in the logger as an argument is a possibility which is hinted at but there might be other options too that are worth exploring.
The quote at the end "Loggers should be injected into dependencies. Full stop." is one possible way, but simply stating that with no examples would probably leave a lot of people wondering what that's all about. For completeness, the possible solution is in an early post of the author, here: https://dave.cheney.net/2017/01/23/the-package-level-logger-anti-pattern
Finally... I hope some gophers would learn something from this Man eventually. Use context.Context when you really need it and do NOT act that like a f. store.
Though I agree with what the author writes I'm a bit disappointed that only that's done is tear down this concept but not really provide good alternatives or examples of how it (c|sh)ould be done instead. Just passing in the logger as an argument is a possibility which is hinted at but there might be other options too that are worth exploring.
The quote at the end "Loggers should be injected into dependencies. Full stop." is one possible way, but simply stating that with no examples would probably leave a lot of people wondering what that's all about. For completeness, the possible solution is in an early post of the author, here: https://dave.cheney.net/2017/01/23/the-package-level-logger-anti-pattern
Finally... I hope some gophers would learn something from this Man eventually. Use context.Context when you really need it and do NOT act that like a f. store.