> And I'm also talking to you, "12-factor app". Shame on you. You could be so great. This single thing makes you incompatible with the entire Unix philosophy.

> And I'm also talking to you, "12-factor app". Shame on you. You could be so great. This single thing makes you incompatible with the entire Unix philosophy. Because it's not a Unix CLI tool... And obviously cluttering stderr with informational messages has downsides too. "stdout for info, stderr for error" works pretty well for servers (what else are you supposed to use stdout for?) It never actually says why this is supposedly bad. This is just repetition of a slogan with zero actual content. I have yet to encounter a "rule" that shouldn't be broken at least on occasion, and without the reasoning you don't know when you're supposed to break it.