On 30-Mar-01 Silviu Cojocaru opined:
> On Fri, 30 Mar 2001, at 00:49 (GMT -0600), ABrady wrote:
>
>> Galeon is getting to be workable. Missing a couple of things and still
>> some infrequent crashes (for me). Requires Mozilla be installed
>> (another
>> memory hog) but, doesn't overload the system with bringing up gobs of
>> useless stuff to go with it. Needs an external mail client.
>>
>> Konqueror works fine. But, doesn't (that I saw) allow an opening page
>> other than your home directory. Also, the bookmarks are a bit unweildy
>> and
>> it brings up lots of k-processes that support it (like most of the
>> other
>> KDE stuff does when run). Doesn't close down cleanly (again, like much
>> of
>> the rest of KDE) because the programmers assumed if you wanted
>> _anything_
>> from KDE to run, you wanted all of it. So, useless processes are left
>> behind after closing.
>
> Maybe you don't understand the way KDE works. Let me shed some light
> here.
> KDE 2.x doesn't start slower then GNOME, for intsance, and it brings up
> enough processes to support whatever could possibly be loaded
> afterwards
> from the KDE suite. All those processes, though memory consumers, are
> intended to speed up app loading (only for ones that come with KDE).
>
> Loading and unloading means lost time, so the processes are only fired
> up
> once, on startup, and then "recycled".
>
> Those processes become useless if, for example, Konqueror, si started
> from
> say... twm or any other window manager and not from within the KDE
> desktop.
No, I understood that perfectly. I wasn't saying there wasn't some minimal
time gain, I was simply saying, unless you use KDE and only KDE, it
leaves a lot of processes behind when closing anything down that uses the
KDE support libraries and processes. While this may be an advantage for
those who use that desktop, it's a PITA for those who (like myself) want
to use the ocassional KDE app and would like for it to clean up after
itself when the support stuff is no longer needed, ala konqueror.
As for gnome, it has numerous problems of its own (I get cores from it
even when I don't run any of its apps, for instance). I also don't care
for its method of leaving useless processes behind, and running stuff
that is pointless (like medusa) simply because it gets installed and it
assumes one is only going to use gnome forever after. This, of course,
applies to those who install things without going through everything
involved with a fine-toothed comb to decide on each and every
installation package, such as when one downloads and installs helix (or,
ximian, I think it's now called) for the first time.
Both have some packages that are superior to what can be found outside of
their environments. To me, the saddest parts are that a) I have to
install everything, including junk I don't want, just to get a few
packages that I like, and b) they have to run a lot of stuff to support
those apps and leave all of the processes behind after the application
that needed them is long gone.
Doing as you describe is advantageous to someone running the
desktop/environment involved. But, I use a light-load wm (icewm and/or
xfce) to minimize drag on the system and would like if some method could
be designed to check for the need of the support stuff and kill it off if
not needed anymore.
---
Earth first! We'll strip-mine the other planets later.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
