QA Team and a Extra Mile Initiative and I would say that they are doing pretty good job nowadays. There hasn't been major bugs that would have affected me in 4.x.0 in a long time and even the first betas are usually working fine but if that isn't enough KDE releases five bug fix releases for every major version.
I think there's something seriously wrong with your distribution if Plasma, Amarok and Nepomuk are crashing or "exploding". I remember Nepomuk crashing in some beta year or two back, Plasma used to crash in the 4.3 times but after that and Amarok has never crashed for me, I think. I'm sure you have reported those bugs for your distribution/KDE?
- Don't show events in the calendar (needs to configure any clock on your desktop!): this prevents akonadi from starting (and with that mysql...). In the same way disable contact runners from KRunner (+ several others you don't need)
- remove anything python-related: no printer applet (forces python2.7! if you have python3.2 configured as your default you may end up with both versions (+PyKDE4-packages!) getting loaded), no python-runners
This should also "fix" startup time.
Probably tuning kwin might help:Quote:
The problem on my users'computers is rather that it slows down the computer like hell, even though there's no obvious 'bug' with opengl.
* change the scale method (kwin desktop effects -> advanced-tab)
* disable blur effect!
* probably disable translucency effect, but that one should not hurt.
I am running kwin on a quite old pre-coregpu (~10 years old) without any problems.
My point of view is that it must be a real pain for distribution to handle all KDE bugs reported by users. It adds a lot of work for them just to triage them. I'm not sure how many distributions actually try to fix KDE (my wild guess: mostly opensuse?), but if they do, it must require a HUGE lot of ressources.
Orzel in KDE bug tracker then you have not reported a single bug for Plasma or Nepomuk (unless I'm missing something). Most seem to be fixed too. If not then please point me to the bugs you are refering to.
Kwin sometimes crashes with the intel driver. It's only very occassionally but it does happen.
Then the taskbar plasmoid even in the 4.10 beta not reliably ordering entries. Just yesterday it stacked two entries.
The real buggy things are the programs that don't belong to kde itself but are kde related like akregator. It segfaulted randomly (probably while fetching feeds) up to 4.10 beta, but I think it stopped now. But it still can't get ordering feeds right. Especially the feed from fefe's blog is bad (http://blog.fefe.de/rss.xml?html). There are entries from phoronix, planet archlinux, smbc, spiked math, etc. randomly "leaking" into it.
First, because if this was true, then we could happily use KDE and just ignore such garbage. But it is not possible. All those so-said "technologies" they are so proud of are deeply connected / interlocked, and this is design decision (or lack of) at the very core of KDE, not in applications. The user is forced to have all this ugly mysql / java / whatever stuff killing his ressources.
Then because i think that (currently) the best part of KDE are some very great applications (okular, gwenview, dolphin, okteta). Unfortunately, indeed, there are a lot of garbage one, and 'akregator' is actually the worse i've seen. Have any developper ever has a look at the code in the last 10 years ? I guess that all those who did died righ away. You can check the logs, only minor stuff is touched (CMakefiles, translations, typos..). No wonder why : this is one of the ugliest code i've ever seen. It's UGLY AS HELL. If you're a developer, just have a look by yourself (be warned, this is frightening). There is some stuff like 3 or more "high-level-concept-i've read design patterns" classes with (Qt-)connections looping between all of them. It's a miracle that the application even starts. When some kind of event happens, an exponential sequence of signals are raised in loop, and it's yet another miracle that it actually stops one day.
I didn't mention konsole in the great applications, even though i use it daily. It is (imho) a very good application, just borked by the great idea to put all konsole shells in only task, so that any problem with one konsole tab will kill all your tabs. Yes, this is still valid, check current konsole code. More or less the same way they do with plasma so that any badly written plasmoid will kill your whole plasma (that is, if plasma doesn't kill itself before). And believe me, there are some very badly written plasmoid.