News for hackers. Stuff that matters.

A comment on Why a Logging Framework Should Not Log. Parent comment

Re:Why a Logging Framework Should Not Log by phillord on Thursday May 05, 2016 @01:52PM (#11638275)
It doesn't force anything though, unless you statically refer to the runtime. It does force you to exclude their logging backend, but that is straight-forward enough.
[ Parent | on HN ]
Re:Why a Logging Framework Should Not Log by theanomaly on Thursday May 05, 2016 @01:59PM (#11638349)
Yes, but you have to know to exclude their backend. And, that library may be several dependencies deep. Now you're expecting potentially junior developers to have the insight to grep their entire transitive dependency tree, find the nop dep, and exclude it. This kind of silent failure is worse than the alternative.
[ Parent | on HN ]
Re:Why a Logging Framework Should Not Log by duaneb on Thursday May 05, 2016 @02:27PM (#11638582)
Dependency exclusions is a code smell everywhere but java. I don't understand why someone is actively giving this advice.
[ Parent | on HN ]
Re:Why a Logging Framework Should Not Log by phillord2 on Thursday May 05, 2016 @03:33PM (#11639057)
The alternative is not specifying a nop dependencies and then inflicting on downstream uses the choice that I was not prepared to make.
[ Parent | on HN ]