.@propensive imperative logging is bad. I'd prefer neither.
You use a third-party library/framework but don't explicitly specify in the code how you want logging to be done. Which would you prefer?
-
-
-
what about a log call(i/o) wrapped by a scalaz Task?
- Show replies
New conversation -
-
-
I think the "correct" answer is obvious... though I'm actually not sure which one you're angling for...!
-
Unified logging is "free" if all point to STDOUT. But if forced to specify it in code, you can direct all to same place.
End of conversation
New conversation -
-
-
Aha, you're right, of course! :)
-
What irks me is the feeling, "it works, but there are 5 places logging may be defined, so which conf is actually being used?"
End of conversation
New conversation -
-
-
a lib should provide logging effects that are tailored to its function. I'm not convinced one can abstract over this.
-
which is to say, traditional logging is an antipattern. But setting that aside, compile error. The logger is a parameter.
End of conversation
New conversation -
-
-
third option: logs errors to stderr
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.