Mac's close action doesn't terminate the program.
Mac's close action doesn't terminate the program.
Mac keeps the app open even after clicking 'close' because of its default behavior, unlike some other systems. The red X stays visible as a reminder that the app isn’t closed until you actively release it. The Cmd+Q shortcut works by sending a signal to terminate the process immediately, but the interface design maintains the close indicator for clarity.
It's likely a quirk with its POSIX roots. I recall back in college we had to log into a server to use an app that launched a GUI. But we're told to go to the menu to close the app rather than close the window, because otherwise the app wouldn't really terminate and a license was eaten up. I could make some guesses why but I'm not certain what the reason is.
I'd guess it was to improve perceived performance -- opening a program that is still open but has no open windows is faster than opening a completely closed program, but has now remained since it was be more annoying to change it at this point.
This approach offers clarity but the idea is to keep the app active in the background once the last window closes, making it seem to start quicker. Some believe it’s better to close unnecessary windows rather than letting them stay open. If someone accidentally closes the final window, they’re frustrated because they have to restart the app.
This approach ensures the apps are prepared for immediate use each time. Adjustments can be made using various tools available in the App Store, such as improved Snap Tool. Keeping the apps open when not in use doesn't significantly impact performance.
I'm discussing how background apps consume battery and processing power.
Only a little. Chrome is still active without affecting power use or speed.
Try the game on your Mac, then close it down. Let me know the battery life and CPU usage afterward.
Ah yes, Chrome is just like a game. And there's a difference between minimizing something and closing the window....