4 ms·
> And then you have a possibly confusing situation where you have two programs that do essentially the same thing My point is, I'd never thought of using yes f
by dncornholio 4y ago
> And then you have a possibly confusing situation where you have two programs that do essentially the same thing
My point is, I'd never thought of using yes for this purpose. So in this case, you could make a command called 'outputsomethingfast' and you could make a command called yes, that internally calls 'outputsomethingfast --output=yes' or something like that.
To me this is way more logical, and more in line with the Linux philosophy, right?
- jraph 4y agoI guess. I don't like the name "yes" and I think we would have been better off with a more general name since the command is general, but now it's there, so… However, this is independent from this optimization, "yes" already had this feature of outputting anything, I think? But I expect this kind of accident to happen in any working system that has been long enough. This seems unavoidable. So we'd better put up with this kind of mess probably.