| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The first question that this brings is:
Is the output of the program useful for a downstream process? Is this
logging an *output* of the program?
But in this case, the answer is: yes, for both questions.
A downstream program could very well be fed the output of the program
via a pipe and process it, as the data being emitted is meant to be
ingested.
So instead of following the default "warnings ought to go to stderr"
model, we acknowledge that the data is actually an *out*put, and send it
to std*out*.
|
