4 ms·
Yeah, but all those tools by default don't print anything if they run successfully, which is indistinguishable from silent failure. If you look at all modern t
by oblio 6y ago
Yeah, but all those tools by default don't print anything if they run successfully, which is indistinguishable from silent failure.
If you look at all modern tools, this approach has been abandoned, especially for long running operations, since it's obviously bad UX.
- TeMPOraL 6y agoRight. That I agree with.
- marcosdumay 6y ago> which is indistinguishable from silent failure What is why the same tools do not have silent failures. And OS failures aren't silent. > If you look at all modern tools, this approach has been abandoned Gladly, you are wrong. Modern tools have indeed add optional noisy modes, nearly all opt-in.
- oblio 6y ago> What is why the same tools do not have silent failures. And OS failures aren't silent. Thankfully, there are no bugs in our software :-) > Gladly, you are wrong. Modern tools have indeed add optional noisy modes, nearly all opt-in. Almost everything network facing (which is almost everything, these days), is verbose by default. Git, curl, etc.
- marcosdumay 6y ago> Thankfully, there are no bugs in our software :-) Yep. Bugs are why OS failures are not silent. But you've got a point. Network facing software need some progress confirmation.
- GuB-42 6y agoYou mean like grep not returning anything when it searched for something and didn't find it? It is more about a lack of feedback than a hidden state. It is a problem but not the same one. Talking about Unix tools, the hidden state would be more like environment variables like the PATH or locale.
- TeMPOraL 6y agoEnvironmental variables are essentially dynamic binding at process level. Super useful, but I wish there was a way for programs to declare what env variables they're using, in a way that can be inspected programmatically. Related: cmdline arguments are essentially lexical binding at process level. I wish there was an idiom there like there is in Lisps (Common Lisp in particular), where a function would take an optional argument whose default value is the value of a dynamic variable. In process terms, that would be declaratively specifying that an optional cmdline parameter takes its default from an environment variable.
- ben509 6y agoOr just some kind of generic way to advertise where they're reading configuration. The worst are programs that search 20 places for configuration, so you have no idea whether you've turned some feature on or off. What I really want is a generic system of algebraic effects for processes so "read configuration" becomes something I can inspect or wrap with my own handler.