As far as I can tell, the red X closes the window but leaves the program running. The yellow minus minimizes the window into the dock.
It seems there is very little purpose to the red X "close but leave running" function. Why bother?
Perhaps in ancient times our forefather's and foremother's machines were so slow and resource bound, that the slight saving of memory and faster startup was an advantage with the red x over quiting the program entirely.
But there also seems to be a drawback to "close but leave running." Namely, when you click on the icon in the dock, or select in the cmd-tab "floating dock" or whatever it is called, you bring the program to the "foreground" but with no windows open. This serves no purpose at all except to drive me nuts, as the system in that case "is not doing what it is supposed to do." Instead it does "nothing."
So I am trying to train myself not to click the red x, to avoid that frustration.
In addition, the subtle difference between the following are somewhat confusing, and I am not yet able to use them efficiently:
It seems there is very little purpose to the red X "close but leave running" function. Why bother?
Perhaps in ancient times our forefather's and foremother's machines were so slow and resource bound, that the slight saving of memory and faster startup was an advantage with the red x over quiting the program entirely.
But there also seems to be a drawback to "close but leave running." Namely, when you click on the icon in the dock, or select in the cmd-tab "floating dock" or whatever it is called, you bring the program to the "foreground" but with no windows open. This serves no purpose at all except to drive me nuts, as the system in that case "is not doing what it is supposed to do." Instead it does "nothing."
So I am trying to train myself not to click the red x, to avoid that frustration.
In addition, the subtle difference between the following are somewhat confusing, and I am not yet able to use them efficiently:
- cmd-w
- cmd-q
- cmd-h
- red X
- yellow minus