9 ms·

Unfortunately, there two different and unrelated features called "Auto Termination", which only muddies the water. One feature aims to preserve system resource

Unfortunately, there two different and unrelated features called "Auto Termination", which only muddies the water. One feature aims to preserve system resources during low memory conditions in way that's completely invisible to the user. The other forcefully removes running applications from the Dock and Command-Tab list even though these apps remain running in the background. My frustration is with the latter feature.

ghshephard 14y ago
To be clear though - Auto Termination of the latter form only occurs if no windows are active. It's basically saying, "If the user no longer has any active documents, and has moved this application to the background, then close it down." Siracusa does a good job describing his annoyance with this feature - and points out that while appropriate for IOS, which has the MRU task switcher, it doesn't work very well on OS X which lacks that metaphor.
- thought_alarm 14y ago
  Yes, that's how it's supposed to work. But there are a bunch of edge cases usability-wise that it fails to handle. It is incredibly thoughtless to automatically quit an app the split second the user switches away from it, particularly if that user explicitly launched the app and has been using it for the last hour. It has always been perfectly acceptable to close all of your windows and then hit Command+N or Command+O to open a new document. And that's even more important now that you must use Command+O to browse your iCloud documents. But if something happens in between those steps, say an email comes in or you need to look something up, then it breaks in a really bad way. It also has nothing to do with iOS. iOS never tries to guess that you've finished working with an app, never prevents you from switching to an app, never removes an app icon from Springboard or task switcher. Indeed, this form of Auto Termination is the exact opposite of how iOS operates. It also has nothing to do with conserving resources. These "terminated" apps remain running the background, consuming memory. The OS simply prevents you from switching back to an app that you were previous using. It is strictly a Windows UI feature, and a very unwelcome one.

ghshephard 14y ago

To be clear though - Auto Termination of the latter form only occurs if no windows are active. It's basically saying, "If the user no longer has any active documents, and has moved this application to the background, then close it down." Siracusa does a good job describing his annoyance with this feature - and points out that while appropriate for IOS, which has the MRU task switcher, it doesn't work very well on OS X which lacks that metaphor.

thought_alarm 14y ago
Yes, that's how it's supposed to work. But there are a bunch of edge cases usability-wise that it fails to handle. It is incredibly thoughtless to automatically quit an app the split second the user switches away from it, particularly if that user explicitly launched the app and has been using it for the last hour. It has always been perfectly acceptable to close all of your windows and then hit Command+N or Command+O to open a new document. And that's even more important now that you must use Command+O to browse your iCloud documents. But if something happens in between those steps, say an email comes in or you need to look something up, then it breaks in a really bad way. It also has nothing to do with iOS. iOS never tries to guess that you've finished working with an app, never prevents you from switching to an app, never removes an app icon from Springboard or task switcher. Indeed, this form of Auto Termination is the exact opposite of how iOS operates. It also has nothing to do with conserving resources. These "terminated" apps remain running the background, consuming memory. The OS simply prevents you from switching back to an app that you were previous using. It is strictly a Windows UI feature, and a very unwelcome one.