3 ms·
It sounds smart but what counts as surprising is entirely context dependent and most programs won't be aware of your context. E.g. a command line app where you
by pydry 3y ago
It sounds smart but what counts as surprising is entirely context dependent and most programs won't be aware of your context.
E.g. a command line app where you put a subtly wrong switch in that does exactly what it thought you wanted and prints nothing while outputting a 0 exit code is dangerous.
- loloquwowndueo 3y agoWhat, like rm -rf ?
- couchand 3y agoIt's about context, of course, but it's not really the program's responsibility to know the user's context. It's the user's responsibility to understand their own context. A tool should have sufficient interlocks to ensure safety when not engaged, but no more.
- 9dev 3y agoI follow your point, however it actually supports mine: An HTTP response isn’t intended to be the output of a command line app. A command line app should take the response from the lower-level HTTP communication and articulate whatever appropriate message to the user, depending on the verbosity level for example. Talking in OSI terms - this is a presentation layer problem, not a link layer one.