[donny2018]

Also, pressing (x) close button doesn’t close the app. It continues hanging somewhere inside of this $1500 machine’s 8GB of RAM.

That alone makes me forget all of the Windows’s quirks and appreciate all the basic things my Windows machine offers.

[williamcotton]

Closing a window has never closed a Mac application. Like, since the first Macs. Applications can have multiple windows so it makes sense from a UX perspective to not terminate an application when a window closes, even if it is the last window.

This behavior can easily be overridden by application developers but they choose not to go against expected behavior.

Power users press Command + Q to quit an application.

I've literally never struggled with what you're describing.

[bigstrat2003]

It makes zero sense from a UX perspective to not terminate (most) processes when the last window closes. Exceptions do exist, but for example if I close all my word processor windows then the process does no good continuing to run. I think you make a fair point that Mac users are used to this behavior and so it should probably remain consistent. But if you were to redesign the OS from the ground up, it's horrible behavior that should in no way be the default.

[dontlaugh]

It's not horrible at all.

You might close all windows, but still have a background task running. That's nicely represented by the app remaining on, which can ask about interrupting the background task if you try to close it. It removes the need for most systray usage.

[jwells89]

That’s because on Mac OS, there isn’t a 1:1 mapping of windows to processes. Instead, multiple windows of any given app are hosted by a single process which stays open when all windows have been closed to facilitate opening documents or new windows without pointlessly disposing of the existing process only to start another.

It’s been like that for the Mac’s entire existence. For someone who’s used Macs all their life, the Windows way is weird.