> Christopher's explanation is a good discussion of the underlying
> mechanics of apps under GUIs on Linux, and I doubt I can improve
> on it. What I can do is give you my actual experience:
> The system I'm typing this on has been running now for 38 1/2 days
> without reboot. I use it for web surfing/email/news, business stuff
> (mostly spreadsheets at the moment), and development in C++ and
> Perl (I'm just learning Perl, so there are lots of errors). I
> run KDE almost exclusively for everything I do - if I do command
> line stuff, I do it in a KDE xterm. I have also installed at least
> half a dozen pieces of software over that period.
Slackware 7.0 for well over 100 days, with basically no problems at all. I've
a couple applications crash on me, but that had nothing to do with the WM, and
didn't do anything to the WM.
Whenever there is a problem, I can kill off the offending program generally with
out touching the WM. When I do have to touch the WM, it NEVER hurts the
rest of the system (yeah, I have to kill the apps that are running over the WM),
haven't rebooted the machine in about 120 days, and that last reboot was because
I upgraded the kernel.
I had KDE and Gnome running on this same machine running RedHat 6.1 for a while,
but it wasn't nearly stable enough for me, and I had to return to Slackware.
I use this machine for image processing, so I need something which is very
stable, and on
which the Window Manager uses very little memory. Slack's stable, and OLVWM is
the most stable, smallest memory hog I've used.