<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">I'm surprised this post keeps coming up. I've been using KDE 4.6.0 since it was a stable release for some years now, I use Kmail too. Problems - virtually zero, some mouse gestures which don't seem to want to be disabled occasionally cause mild annoyance and that terrible indexing utility that logged everything I did and seemed bent on wearing out my hard drives just had to be disabled as much as it can be. It also slowed everything down. I run a fairly heavily loaded desktop and fairly recently started having disc thrashing problems. Added more memory and that has more or less gone away. The fact that it hasn't gone completely is down to me and my use and the memory capability of the motherboard. When I upgraded from KDE 3 I also had to fit a new graphics card to keep the effects running. It's nothing really special just a mid
range cheap part from Nvidia - also most importantly had to add there driver.<br><br>I might reboot/turn off my machine every 6 months or so. One gremlin. Some how closing an app on the task bar just offered me remove from taskbar - it did and the icon just wouldn't come back. In the end I deleted the task bar and added it again and all was ok.<br><br>I suspect the answer to the complaints in these posts is to get real. Linux plus what ever has never ever been completely stable if people run the latest and greatest. Even less so if they compile something like KDE themselves or worse still build up everything from scratch. Distro's are intended to get round these problems according to the level people want. They always have been. Some people don't mind the bugs, others like me just want to use my machine and bug report on stable releases but not to KDE. There wouldn't be any point. I post to the distro. I suppose I have been using KDE plus linux for near
20 years now.<br><br>If someone wants a truly upfront distro where others usually sort out problems quickly I would suggest they try Arch - if they have the ability but in that case they may be able to sort it out themselves..<br><br>Me well I will be upgrading shortly to another stable distro release - new machine too. I've been using this one for 10+ years<br><br>John<br>-<br><div><span><br></span></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font size="2" face="Arial"> <b><span style="font-weight:bold;">From:</span></b> dE <de.techno@gmail.com><br> <b><span style="font-weight: bold;">To:</span></b> kde@mail.kde.org <br> <b><span style="font-weight:
bold;">Sent:</span></b> Tuesday, 7 May 2013, 16:32<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [kde] Yet another failed KDE release?<br> </font> </div> <div class="y_msg_container"><br><div id="yiv0772317710">
<div>
<div class="yiv0772317710moz-cite-prefix">On 05/07/13 20:03, Kevin Krammer wrote:<br>
</div>
<blockquote type="cite">
<pre>On Tuesday, 2013-05-07, James Tyrer wrote:
</pre>
<blockquote type="cite">
<pre>On 03/19/2013 09:58 AM, dE . wrote:
</pre>
</blockquote>
<pre></pre>
<blockquote type="cite">
<pre>The KDE development team appears to be interested in something other
than producing a stable release. It really is that simple.
</pre>
</blockquote>
<pre>Well, simple and false :)
Mostly because the conclusion is based on a misconception regarding KDE to be
a single product.
KDE is a software vendor with several dozend products, each developed by
different people. Sometimes single developers, sometimes teams.
Hence no such thing as a "KDE development team" exists as an entity by itself.
</pre>
<blockquote type="cite">
<pre>As a
result, the release process is not oriented towards producing a stable
release.
</pre>
</blockquote>
<pre>As a result obviously also false, i.e. a non-existing entity doesn't have
goals.
Unless we employ thinking similar religious faith and assume an unobservable
entity exists by people believing in it ;-)
</pre>
<blockquote type="cite">
<pre>I find very useful the dystopian novel: "The Rise of the Meritocracy"
which is a critique of the idea of "the meritocracy". A meritocracy is
defined by the search for merit -- but that is dependent on the
definition of merit. I find that I have no merit in the KDE project
despite the fact that I went to college and studied EE and computer
science. In the KDE project, you obtain merit be designing a new
application. So, that is the nail that everyone is hitting with their
hammer.
</pre>
</blockquote>
<pre>Also not true.
Most contributors at KDE are neither the designers nor maintainers of
applications.
A lot of contributors are not even coders or not contributing other things
than writing code.
Merit is gauged by the quality, reliability and dedication to the contribution
area. In other words merit and recognition is earned through actual
contribution, but that contribution can be a lof ot things other than code.
This applies to the work on KDE activities and products but also to the
foundation managing KDE's legal assets, KDE e.V.
As a sample, the e.V.'s board of directories has currently one member out of
five who's active contribution at the moment is code.
</pre>
<blockquote type="cite">
<pre>I don't want to do that. I want to improve applications. That is what
engineers do; we find the faults with things and fix them -- we improve
things.
</pre>
</blockquote>
<pre>Sounds like a great opportunity then :)
</pre>
<blockquote type="cite">
<pre>Unfortunately, everyone designing new applications from square one is
not conducive to building a stable and bug free desktop environment.
</pre>
</blockquote>
<pre>While only a fraction of developer work on applications of the desktop
environment product, I'd say that even this is a over generalisation even for
those.
The only two applications in that category that I can come up with from the
top of my head which have been "newly" introduced are Plasma Desktop and
Dolphin. Most others, e.g. KWin, Klipper, KMix, have existed for ages.
And while some developers on some of these applications might be more
adventurous than others or developers on non desktop environment applications,
I hadn't had an issue with any of those in quite some time.
</pre>
<blockquote type="cite">
<pre>There is nothing wrong with KDE that a few committed software engineers
-- committed to quality -- couldn't fix. But, I don't think that the
hackers would like it.
</pre>
</blockquote>
<pre>Well, being a conclusion based on a faulty analysis makes its content
impossible to evaluate, but assuming for a moment that the analysis had not
been wrong, then the only conclusion we could draw would be that there are
either not software engineers committed to quality or that they have so far
abstained from contributing their skills.
Cheers,
Kevin
</pre>
<br>
<fieldset class="yiv0772317710mimeAttachmentHeader"></fieldset>
<br>
<pre>___________________________________________________
This message is from the kde mailing list.
Account management: <a rel="nofollow" class="yiv0772317710moz-txt-link-freetext" target="_blank" href="https://mail.kde.org/mailman/listinfo/kde">https://mail.kde.org/mailman/listinfo/kde</a>.
Archives: <a rel="nofollow" class="yiv0772317710moz-txt-link-freetext" target="_blank" href="http://lists.kde.org/">http://lists.kde.org/</a>.
More info: <a rel="nofollow" class="yiv0772317710moz-txt-link-freetext" target="_blank" href="http://www.kde.org/faq.html">http://www.kde.org/faq.html</a>.</pre>
</blockquote>
<br>
There is no misconception. KDE is always giving problems. Look at
the bugzilla crawling with stale bugs.<br>
<br>
I thought this thread was dead.<br>
</div>
</div><br>___________________________________________________<br>This message is from the kde mailing list.<br>Account management: https://mail.kde.org/mailman/listinfo/kde.<br>Archives: http://lists.kde.org/.<br>More info: http://www.kde.org/faq.html.<br><br></div> </div> </div> </blockquote></div> </div></body></html>