Silent Accept is Dead :/

In the old days, Unix commands would, when fired, either make a silent accept or an error. That is, if you sent a command to a shell they would by default not spew out any information on the standard output unless something was wrong. Today, silent accept is dead. We have to supply -q parameters to programs to make them behave and not pester our command lines with information. This is a shame because confirmation messages tend to clutter up the screen a lot. Want to do a secure copy over ssh? Then you get information back for each line copied. Want to execute make(1)? You will see endless lines of compilation messages by default and I am pretty sure nobody reads them. Want to view a movie in mplayer? Many lines of output. For some applications, "quiet" is not quiet enough. They have the --quiet-and-i-fsck-mean-it! option to help you quell their responses. It is a shame that the terseness of the Unix command-line has been destroyed by this. I think the problem is cognitive: Scrolling lines of text by will make you miss the context totally when you come back to the display later after your scp has completed. You don't know what the context were, so you will search in the history for the last command executed to figure out what you were doing. Then you will fire off another command, leave the terminal. This cycle then repeats itself. I would love for Silent Accept to come back. I urge you to make it the default. I urge you to take the original ideas of Unix and protect them.