Hacker News new | ask | show | jobs
by tescocles 1246 days ago
...close the app then?

It's just a different paradigm. It's not like quitting the app is in any way difficult (it's just cmd+Q which I actually find a bit too easy to trigger by accident sometimes), it's just Macs don't consider an app to be the sum of its windows.
2 comments
blacksmith_tb 1246 days ago
Sure, it's not hard to hit cmd-q instead of cmd-w, I think the general question is "what's the benefit to me, the user, of having an app still running (and in memory, until it gets paged out to disk) without any windows open?" Obviously there are some kinds of apps that it makes sense to have running in the background all the time, but we're talking about text or image editors, say. I find it to be sort of annoying.
link
Tagbert 1246 days ago
For document apps, the idea is that you are working on a document. You can then close that document and open another document without the app closing when you close the first document. It’s not really about having apps running in the background. It’s just a slightly different way to look at documents and apps.
link
blacksmith_tb 1246 days ago
I guess that suggests an over-optimization in favor of working on more of the same documents eventually - but I might not do that any time soon... I opened an app, edited a document in it. When I am done, unless I have other files open in that app, it seems like it might as well be completely closed, until I launch it again or open one of the document types associated with it? I guess some users may only work on a few kinds of files, and in a few apps, so they might benefit from slightly quicker load times; otherwise having a bunch of things running on the off chance I use one again seems like a waste of RAM.
link
Tagbert 1245 days ago
…and in that case, you would close the app.

Conflating closing a document window with closing the app seems like a strange constraint.

link
ziml77 1246 days ago
The behavior is archaic though. I've mentioned this in comments before, but the design really only makes sense if you look back at how macOS used to work. Only one application would be running at a time. To get to another application (including Finder), you had to quit the running application. In that context, it's a bit more reasonable to have an application running without any windows.
link