On 02/03/2012, at 3:01 AM, LuKreme wrote: > You simply have the OS try to send a quit to the app. After a certain amount > of time, send a kill. That certain amount of time is likely to be somewhere > north of a minute, but south of 5. > > At a certain point, killing the process is the only way to continue. If the > data is lost, it's already lost.
I agree with this, the user wants to quit, if the OS can correctly determine that the application is truly borked then it can just kill the app or notify the user that this is what is going to happen (and data may be lost). That said, I think it is relatively that clear Apple is moving towards an iOS like approach on OS X where apps autosave and are never usually quit by the user, but just hibernate when not being actively used and resources become low. Perhaps in an OS X environment, with virtual memory, this may just mean 99% of app data is moved to disk, rather than actually terminating the app, which I believe is what happens in iOS (as it doesn't have VM). I also wouldn't be surprised if we eventually lose "Quit" from the "File" menu. Leaving some way, perhaps from the Doc or just "Force Quit ..." to quit (or kill) an app if really needed. Quite a long way off though. Cheers, Ashley. -- Ashley Aitken Perth, Western Australia (GMT + 8hrs!) Social (Facebook, Twitter, Skype etc.): MrHatken Professional (LinkedIn, Twitter, Skype etc.): AshleyAitken _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
