Perhaps an analogy would help. Anne and many of us have said the same thing in at least 50 threads over the last six months. Would she (and the rest of us) be better off just putting her response in a notepad file and cut and paste it into threads like this? Or is it better to retype it over and over and over again?
Same logic applies to the apps people want to kill. You can kill them over and over and over or simply let the o/s get rid of them when it needs to do so. Otherwise, those apps are available (like a notepad file) to be used again without restarting them.
If you want to see what is going on with your o/s get "System Panel." Then reboot your system. When you view the System Panel report you'll see that there are some "active" applications as well as some inactive "cached" applications that begin automatically when the system is booted.
You'll see that the inactive applications use a few seconds of CPU time (i.e cycles) and then remain quiet. Some of the "active" applications also use a few seconds of CPU time and then slip into the "background." A few apps are "services;" they use a few cycles to keep track of what is going on and otherwise, they consume few cycles.
At any one time, only one or perhaps two or three apps are in the "foreground," actively using cpu cycles.
As long as you have 30+ mgs of memory available, there is no reason for the o/s to close down an app when a new app demands resources. And as long as apps are quietly sitting in the background or are in cache there is no reason to kill them. Doing so is like clearing a half filled ballroom of dancers because other dancers might want to come in and dance.
So even if a task killer isn't needed, does it do any harm? Potentially, yes. Killing an active app may cause it to leave data and cache in place that it would have otherwise cleaned up. Over time, that slows down the system. Even worse, killing a running application can make the entire system unstable.
The only reasonable justification for killing an application is that it has "gone rogue" and is using resources that the o/s needs for other purposes. But since it is difficult to determine if that is true, a much better approach is simply to restart the o/s and see if the behavior recurs. If it does, get rid of the app.
