Unix: Why Not Stdlog?
3 by AtlasBarfed | 1 comments on Hacker News.
Setting aside recent hipster posts about logging being dead... I continually run into the issue when making CLI apps: where does logging go? stdout is terrible, logging would pollute information you want piped to other programs and is noise stderr isn't great, because log messages are more status than errors, and usually breaks error detection, handling, and processing. Most logging frameworks I've seen belch to stdout or stderr by default. Yuck. Most alternatives (enabled by logging frameworks) is a logfile is ... ok, but then you have logfiles polluting your FS in arbitrary locations, and the logfile location and name is going to be highly unstandardized. So why isn't there a standard notion of stdlog in UNIXland alongside stdin, stdout, and stderr?