4 ms·
Apple’s current implementation certainly is dodgy but I think the ultimate goal is very desirable. Whenever I explain the difference between quitting and closin
by ugh 15y ago
Apple’s current implementation certainly is dodgy but I think the ultimate goal is very desirable. Whenever I explain the difference between quitting and closing a window on OS X to someone their eyes glaze over (even when I ignore all the inconsistencies). It’s just something no casual user understands. Nobody has the same problem when using iOS.
The transition period will be rocky and the UI in OS X is currently still very much optimized for the old model but I think Apple is walking in the right direction.
- Zak 15y agoMaking quit-on-close a UI recommendation for things that don't naturally run as a background service with no visible UI might be a cleaner solution.
- ugh 15y agoI guess I would actually like all apps to quit on close. Apps that need it should be able to run in the background (sans any indicator that they are still running). If all apps auto save and restore their state only very few apps actually need to run in the background: mail clients, music players, RSS readers, … The dock could then show all apps with open windows (including hidden or minimized open windows) and Cmd-Tab could show recently used apps (including apps that are not running). For this to work seamlessly all apps need to be able to auto save and restore state and all apps need to be sane about whether or not they need to run in the background. That’s certainly a daunting task and it’s understandable why Apple can’t (and won’t?) jump right to that.