Kde 4.x stability

Now the plasma and the plasmoids are executed in a single process . It is not a good practice since there is a risk of instability whenever a plasmoid crashes . Third party plasmoids usually have a number of bugs . So installing a third party plasmoid give rise to system instability. To avoid these , I suggest the execution of plasma and plasmoids in two seperate processes..


      Explore your hobbies and interests. Go to http://in.promos.yahoo.com/groups/

_______________________________________________
kde-quality mailing list
kde-quality@...
https://mail.kde.org/mailman/listinfo/kde-quality

[Aaron J. Seigo]

On Tuesday 16 June 2009, Praveesh K P wrote:
> these , I suggest the execution of plasma and plasmoids in two seperate
> processes..

while dataengines might be able to run out of process at some point (though
with extra overhead coming with it), it's absurd to run widgets in their own
processes. this is not a web browser where each item lives in its own separate
tab in isolation and which is allowed to take 100s and 100s of MB of RAM just
because it can.

the real answer to stability is dynamic languages, and there are enough
advantages to using those languages (such as network installation and speed of
devel) that this will happen naturally over time, i think.

if you'd like to help improve things, please consider helping work on the
plasma ScriptEngines. the full JavaScript bindings were halted when the
developer became too busy to continue on it (so we have just the simplified
bindings, which are useful but not enough to cover every single situation) and
they need documenting.

--
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software



_______________________________________________
kde-quality mailing list
kde-quality@...
https://mail.kde.org/mailman/listinfo/kde-quality