OS X Lion grows similarity with IOS in the way it manages applications to decide for itself the closure of an application to free resources. This function of "automatic termination" of applications, a real break from the multitasking system is supposed to improve "user experience" according to Apple. The Cupertino company said that the role of traditional + Q is minimized with OS X Lion, the benefit of an automatic management of application state - the beta of OS X Lion pushed to its logical conclusion by not doing the lights appear in the Dock. Lion OS X has two distinct ways to leave, or rather interrupting an application automatically.
The first, "Sudden Termination", which must be provided by the developer, allows an application to tell the system it can be left without further ado, allowing particular to expedite the process of extinction of the machine or log off. The second, the "Automatic Termination" is a bit more invasive. Again, the developer decides to implement it or not: if it does, Apple advises that the application is also compatible with automatic backup and Resume. The Automatic Termination is indeed a function allowing the system to close an application when it wants to free up resources. A good application to test this feature is TextEdit . TextEdit open some documents, close them, go about your business, do a Command + Tab to go back to TextEdit ... and notice that the application closed. The Automatic Termination works even if the documents are still open, provided that the application is not used (not active, no documents or minimized in the Dock visible to the user) allow multiple documents open TextEdit in a space, and again, go about your business. Sooner or later, OS X TextEdit Lion close to free resources. TextEdit is not in the Dock and for good reason: it was left automatically by Lion. It appears, against the Activity Monitor, as if to sleep. Disadvantage: If you did not add its icon in the Dock, you should use your favorite launcher or the Finder to open it again. TextEdit is actually not quite left: the process still appears in the Activity Monitor. The recovery is instant, and with the Auto Save and Resume, documents and their contents are restored. Few resources are actually released: this function is really useful, or she may cause the confusion? The implementation of this function is left to the discretion of the developer, but the user should not be allowed to disable it anyway? Does the user to manage the state of its applications, or machine?
The first, "Sudden Termination", which must be provided by the developer, allows an application to tell the system it can be left without further ado, allowing particular to expedite the process of extinction of the machine or log off. The second, the "Automatic Termination" is a bit more invasive. Again, the developer decides to implement it or not: if it does, Apple advises that the application is also compatible with automatic backup and Resume. The Automatic Termination is indeed a function allowing the system to close an application when it wants to free up resources. A good application to test this feature is TextEdit . TextEdit open some documents, close them, go about your business, do a Command + Tab to go back to TextEdit ... and notice that the application closed. The Automatic Termination works even if the documents are still open, provided that the application is not used (not active, no documents or minimized in the Dock visible to the user) allow multiple documents open TextEdit in a space, and again, go about your business. Sooner or later, OS X TextEdit Lion close to free resources. TextEdit is not in the Dock and for good reason: it was left automatically by Lion. It appears, against the Activity Monitor, as if to sleep. Disadvantage: If you did not add its icon in the Dock, you should use your favorite launcher or the Finder to open it again. TextEdit is actually not quite left: the process still appears in the Activity Monitor. The recovery is instant, and with the Auto Save and Resume, documents and their contents are restored. Few resources are actually released: this function is really useful, or she may cause the confusion? The implementation of this function is left to the discretion of the developer, but the user should not be allowed to disable it anyway? Does the user to manage the state of its applications, or machine?
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.