🚀 go-pugleaf

In article <33pmgah.messina@netcom.com>, messina@netcom.com 
(Tony Porczyk) writes:
|> boyd@prl.dec.com (Boyd Roberts) writes:
|> 
|> >In article <7=pmx9.messina@netcom.com>, messina@netcom.com (Tony Porczyk) writes:
|> >> 
|> >> BTW, since when is stderr reserved for "non-information"?  Frankly, I
|> >> say send to stderr anything that is non-essential in the redirection of
|> >> stdout or in piping of stdout, such as sorting.
|> 
|> >Standard error is for _errors_.
|> >If it's `non-essential' then don't output it in the first place.
|> 
|> Do you get all those answers from a book?  Let me ask you a question -
|> does a usefulness of a utility make any difference, or is it all
|> according to what you found written somewhere?  I mean, have you ever
|> tried being *flexible* to accomplish your task? 
|> 
|> t.

I have seen very many flexible solutions to problems, many of them were
even good solutions, for a while at least. The usual result is that
some time in the future the flexible solution breaks and someone has to
do it right. 

I wish that I could quote the fortune on experience but my memory is
being a little too flexible today.

-- 

Michael Salmon

#include	<standard.disclaimer>
#include	<witty.saying>
#include	<fancy.pseudo.graphics>

Ericsson Telecom AB
Stockholm