<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Trinity and the Challenges of Continuing KDE 3</title>
	<atom:link href="http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/</link>
	<description>Sebastian Kügler&#039;s web log</description>
	<lastBuildDate>Fri, 27 Jan 2012 23:36:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: sebas</title>
		<link>http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/comment-page-1/#comment-523</link>
		<dc:creator>sebas</dc:creator>
		<pubDate>Tue, 01 Jun 2010 08:32:26 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/#comment-523</guid>
		<description>&quot;&lt;i&gt;Can you honestly tell us that KDE 4 is as intuitive, feature rich, and generally ready for prime-time as KDE 3.5.x?&lt;/i&gt;&quot;

In the majority of aspects, it&#039;s even a lot better. So yes.</description>
		<content:encoded><![CDATA[<p>&#8220;<i>Can you honestly tell us that KDE 4 is as intuitive, feature rich, and generally ready for prime-time as KDE 3.5.x?</i>&#8221;</p>
<p>In the majority of aspects, it&#8217;s even a lot better. So yes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RevLinux</title>
		<link>http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/comment-page-1/#comment-515</link>
		<dc:creator>RevLinux</dc:creator>
		<pubDate>Mon, 31 May 2010 23:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/#comment-515</guid>
		<description>This is not the place or platform to report specific bugs.

My point is simply that most of the Linux community in general knows that KDE 4.x was released before it was ready. Can you honestly tell us that KDE 4 is as intuitive, feature rich, and generally ready for prime-time as KDE 3.5.x? I understand how anyone close the the project would feel pride with the work they&#039;ve done so far, and I wouldn&#039;t take anything away from that. I&#039;m not here to tear down the accomplishments of KDE 4. However, it is my opinion along with many other people that it was rushed out the door before it possessed the level of usability of the existing platform.

KDE 4 has great potential that we hope is achieved soon.
When you quoted statistics on how many people are using KDE 4.x, does it account for how many users felt they had little or no choice because their current apps would no longer be maintained or supported on the older platform?

I say these things because I want KDE 4 to succeed, not tear it down.
I&#039;m also attempting to point out that there&#039;s an element of group-think surrounding the KDE project, and it&#039;s causing those involved with the project to be blinded to some important things. I know it is hard for some people to listen to what I&#039;m saying with an open mind, and it will likely turn off some folks. However, we need to have an open &amp; honest discussion if we want KDE &amp; Linux in general to achieve greatness.

KDE users loudly voiced their disapproval when KDE 4.x was initially released, and the din gradually faded as users came to believe and/or accept that they had to settle with the options presented to them when their distros moved to the new platform in the name of progress. If you doubt my claims about how users felt, Google is your friend. ;)

This article says it all in the following paragraph:

http://www.itlure.com/2010/05/trinity-project-picks-up-where-kde-3510.html

The Trinity Project Picks Up Where KDE 3.5.10 Left Off
Posted by Danny on Tuesday, May 25, 2010
Labels: KDE 3.5.10, Kubuntu, Legacy, Linux News, old school

&quot;Hey, pst! Yes, you! I know you&#039;ve been crying yourself to sleep at night ever since those mean, mean people developing the K Desktop Environment decided to radically change the way your favorite DE worked and release the dreaded &quot;4&quot; version. Good news! There&#039;s no more need to get over it and move on with your life, as, apparently, the God of open source decided to bring you a fork of KDE 3.&quot;

Did the folks at KDE know about and listen to the real user feedback, or was it filtered by their own perceptions?
If we all want KDE 4 to be great, then we have to be open to criticism and feedback from end users.
My end users are telling me that KDE 4.x makes their computing experience more difficult instead of improving their computing experience. If you use Google, you will see that the feedback says KDE 4 is improving but isn&#039;t ready for prime-time yet.

Trinity is one of many responses that can take place when a new platform disorients and/or alienates users.

Just for the record, we don&#039;t &quot;lean back and wait until others have solved all our problems&quot;, my devs have contributed to both our upstream distro and to KDE. As founder of our distro, I insist on my devs doing so :)
This post is one of many ways that we are active and contribute to the community, in the form of open discussion as well as code and bug reports. These types of honest discussions are just as important as any other process in the open source community as a whole. I donate money to projects we rely on as well. ;)

We are a small distro and not publicly released yet, but we believe in open source.
Open source also needs to have open discussion in order to ultimately succeed. :)</description>
		<content:encoded><![CDATA[<p>This is not the place or platform to report specific bugs.</p>
<p>My point is simply that most of the Linux community in general knows that KDE 4.x was released before it was ready. Can you honestly tell us that KDE 4 is as intuitive, feature rich, and generally ready for prime-time as KDE 3.5.x? I understand how anyone close the the project would feel pride with the work they&#8217;ve done so far, and I wouldn&#8217;t take anything away from that. I&#8217;m not here to tear down the accomplishments of KDE 4. However, it is my opinion along with many other people that it was rushed out the door before it possessed the level of usability of the existing platform.</p>
<p>KDE 4 has great potential that we hope is achieved soon.<br />
When you quoted statistics on how many people are using KDE 4.x, does it account for how many users felt they had little or no choice because their current apps would no longer be maintained or supported on the older platform?</p>
<p>I say these things because I want KDE 4 to succeed, not tear it down.<br />
I&#8217;m also attempting to point out that there&#8217;s an element of group-think surrounding the KDE project, and it&#8217;s causing those involved with the project to be blinded to some important things. I know it is hard for some people to listen to what I&#8217;m saying with an open mind, and it will likely turn off some folks. However, we need to have an open &amp; honest discussion if we want KDE &amp; Linux in general to achieve greatness.</p>
<p>KDE users loudly voiced their disapproval when KDE 4.x was initially released, and the din gradually faded as users came to believe and/or accept that they had to settle with the options presented to them when their distros moved to the new platform in the name of progress. If you doubt my claims about how users felt, Google is your friend. ;)</p>
<p>This article says it all in the following paragraph:</p>
<p><a href="http://www.itlure.com/2010/05/trinity-project-picks-up-where-kde-3510.html" rel="nofollow">http://www.itlure.com/2010/05/trinity-project-picks-up-where-kde-3510.html</a></p>
<p>The Trinity Project Picks Up Where KDE 3.5.10 Left Off<br />
Posted by Danny on Tuesday, May 25, 2010<br />
Labels: KDE 3.5.10, Kubuntu, Legacy, Linux News, old school</p>
<p>&#8220;Hey, pst! Yes, you! I know you&#8217;ve been crying yourself to sleep at night ever since those mean, mean people developing the K Desktop Environment decided to radically change the way your favorite DE worked and release the dreaded &#8220;4&#8243; version. Good news! There&#8217;s no more need to get over it and move on with your life, as, apparently, the God of open source decided to bring you a fork of KDE 3.&#8221;</p>
<p>Did the folks at KDE know about and listen to the real user feedback, or was it filtered by their own perceptions?<br />
If we all want KDE 4 to be great, then we have to be open to criticism and feedback from end users.<br />
My end users are telling me that KDE 4.x makes their computing experience more difficult instead of improving their computing experience. If you use Google, you will see that the feedback says KDE 4 is improving but isn&#8217;t ready for prime-time yet.</p>
<p>Trinity is one of many responses that can take place when a new platform disorients and/or alienates users.</p>
<p>Just for the record, we don&#8217;t &#8220;lean back and wait until others have solved all our problems&#8221;, my devs have contributed to both our upstream distro and to KDE. As founder of our distro, I insist on my devs doing so :)<br />
This post is one of many ways that we are active and contribute to the community, in the form of open discussion as well as code and bug reports. These types of honest discussions are just as important as any other process in the open source community as a whole. I donate money to projects we rely on as well. ;)</p>
<p>We are a small distro and not publicly released yet, but we believe in open source.<br />
Open source also needs to have open discussion in order to ultimately succeed. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pedro</title>
		<link>http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/comment-page-1/#comment-508</link>
		<dc:creator>Pedro</dc:creator>
		<pubDate>Mon, 31 May 2010 16:08:44 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/#comment-508</guid>
		<description>Strangely the link to the project wasn&#039;t posted together with this blog entry.  I just found it:
http://trinity.pearsoncomputing.net/</description>
		<content:encoded><![CDATA[<p>Strangely the link to the project wasn&#8217;t posted together with this blog entry.  I just found it:<br />
<a href="http://trinity.pearsoncomputing.net/" rel="nofollow">http://trinity.pearsoncomputing.net/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pedro</title>
		<link>http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/comment-page-1/#comment-507</link>
		<dc:creator>Pedro</dc:creator>
		<pubDate>Mon, 31 May 2010 16:04:32 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/#comment-507</guid>
		<description>I hope they succeed, as I really like KDE 3 and I think KDE 4 is going in the wrong direction in so many different ways.
I will be one of their users, as I want to go back to KDE.  I tried for a while to use KDE 4, but had to switch to FVWM since KDE 3 doesn&#039;t build for me anymore.

Thanks for the effort!</description>
		<content:encoded><![CDATA[<p>I hope they succeed, as I really like KDE 3 and I think KDE 4 is going in the wrong direction in so many different ways.<br />
I will be one of their users, as I want to go back to KDE.  I tried for a while to use KDE 4, but had to switch to FVWM since KDE 3 doesn&#8217;t build for me anymore.</p>
<p>Thanks for the effort!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sebas</title>
		<link>http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/comment-page-1/#comment-505</link>
		<dc:creator>sebas</dc:creator>
		<pubDate>Mon, 31 May 2010 12:19:59 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/#comment-505</guid>
		<description>KDE 4 will never support every feature that KDE 3.5 did. 4 does however contain a number of features that 3.5 never had, and can do many of the things that 3.5 could do, but in a much more elegant way. You have to take into account that 3 and 4 are just very different beasts, and that with KDE 3.5 technology, many things we do today, and we&#039;ve come to rely on were simply not possible.

As to forcing people to use something, that statement is ridiculous. Firstly, KDE never forced anybody to use the 4 version. In fact, we&#039;ve been very clear as to the status of the 4 series, and have since the release of 4.0 spent ridiculous amounts of time on improving its stability and completeness -- and that&#039;s very visible.  If your distro automatically updates you to a version you don&#039;t want, choose another distro or pay more attention to the software you&#039;re installing. 

As to comparing anything here to rape, that&#039;s completely out of proportion, please tone down.</description>
		<content:encoded><![CDATA[<p>KDE 4 will never support every feature that KDE 3.5 did. 4 does however contain a number of features that 3.5 never had, and can do many of the things that 3.5 could do, but in a much more elegant way. You have to take into account that 3 and 4 are just very different beasts, and that with KDE 3.5 technology, many things we do today, and we&#8217;ve come to rely on were simply not possible.</p>
<p>As to forcing people to use something, that statement is ridiculous. Firstly, KDE never forced anybody to use the 4 version. In fact, we&#8217;ve been very clear as to the status of the 4 series, and have since the release of 4.0 spent ridiculous amounts of time on improving its stability and completeness &#8212; and that&#8217;s very visible.  If your distro automatically updates you to a version you don&#8217;t want, choose another distro or pay more attention to the software you&#8217;re installing. </p>
<p>As to comparing anything here to rape, that&#8217;s completely out of proportion, please tone down.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sebas</title>
		<link>http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/comment-page-1/#comment-504</link>
		<dc:creator>sebas</dc:creator>
		<pubDate>Mon, 31 May 2010 12:07:22 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/#comment-504</guid>
		<description>If you decide to provide KDE 3.5, that&#039;s fine as I mention in my above blog already. I&#039;m also outlining some problems when shipping KDE 3.5. Ultimately, it&#039;s a trade-off of course: Is supporting KDE 3.5 and Qt3 on your own more effective than working with the rest of the ecosystem on 4? This is a question only you, and your users can answer. For the vast majority of others, the answer is the latter.

Can you give some example bugnumbers your users suffer most from, or haven&#039;t those been reported and triaged yet? You can just lean back and wait until others have solved all your problems. For others to work on those issues you seem to be facing, your participation is needed, though. So I&#039;m not sure your attitude of vague statements about quality, and &quot;armchair developer&quot; statements such as telling others to pull software which is in use for nearly two and a half years  by millions of people. How would one be able to do that, by the way? And if one did, how would not releasing updates help any users at all?

I personally find my KDE 4 desktop to be working well and stable. Of course that is highly dependant on the use case, and on the underlying platform. Stability seems to vary between various distributions, so if ReveLinux has problems with KDE 4, comparing your underlying stack (Xorg and driver versions, among others) to other distros might give you some clue. Especially graphics performance seems to vary a lot (in general, I find the newest Free drivers for intel and ATI working best).</description>
		<content:encoded><![CDATA[<p>If you decide to provide KDE 3.5, that&#8217;s fine as I mention in my above blog already. I&#8217;m also outlining some problems when shipping KDE 3.5. Ultimately, it&#8217;s a trade-off of course: Is supporting KDE 3.5 and Qt3 on your own more effective than working with the rest of the ecosystem on 4? This is a question only you, and your users can answer. For the vast majority of others, the answer is the latter.</p>
<p>Can you give some example bugnumbers your users suffer most from, or haven&#8217;t those been reported and triaged yet? You can just lean back and wait until others have solved all your problems. For others to work on those issues you seem to be facing, your participation is needed, though. So I&#8217;m not sure your attitude of vague statements about quality, and &#8220;armchair developer&#8221; statements such as telling others to pull software which is in use for nearly two and a half years  by millions of people. How would one be able to do that, by the way? And if one did, how would not releasing updates help any users at all?</p>
<p>I personally find my KDE 4 desktop to be working well and stable. Of course that is highly dependant on the use case, and on the underlying platform. Stability seems to vary between various distributions, so if ReveLinux has problems with KDE 4, comparing your underlying stack (Xorg and driver versions, among others) to other distros might give you some clue. Especially graphics performance seems to vary a lot (in general, I find the newest Free drivers for intel and ATI working best).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RevLinux</title>
		<link>http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/comment-page-1/#comment-496</link>
		<dc:creator>RevLinux</dc:creator>
		<pubDate>Mon, 31 May 2010 04:03:25 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/#comment-496</guid>
		<description>KDE 4.4 is nowhere close to prime time, and never should have been released yet. Anyone working on developing the KDE 4.x platform should know it or they are fooling themselves. If KDE 4.x is up to 4.4 and yet still crashes as much as it does, then the KDE folks are not using a proper quality control and revision system. This platform is not ready for 4.0 status, let alone 4.4/4.5 status. It hasn&#039;t been properly tested and patched for those revision numbers.

I&#039;m the founder and lead developer of a KDE based distro. Our distro is still using KDE 3.5 because many of our users practically hate KDE 4.x because of lack of usability/features &amp; serious crashes. KDE 4.x is bloated and performs poorly compared to KDE 3.5.x. We applaud the Trinity team for their efforts in maintaining KDE 3.5.x at least until KDE 4 is no longer performing like a late alpha/early beta. I&#039;m not against change or progress, but change just for the sake of &quot;progress&quot; is an exercise in vanity, and changing version numbers does not make a project stable. Especially if the newer product simply cannot do what the former can do, or is many times less stable than the previous version! 

Even though we are a small and very recent distro, we are now looking to see if there&#039;s some way our 4 person dev team can help the Trinity project. I would encourage other dev teams look into doing the same thing until KDE actually releases a product worthy of normal use by Linux users.

KDE should pull KDE 4.x out of production and maintain/support KDE 3.5.x until KDE 4.x is truly a stable, feature-rich product that is actually ready to use.</description>
		<content:encoded><![CDATA[<p>KDE 4.4 is nowhere close to prime time, and never should have been released yet. Anyone working on developing the KDE 4.x platform should know it or they are fooling themselves. If KDE 4.x is up to 4.4 and yet still crashes as much as it does, then the KDE folks are not using a proper quality control and revision system. This platform is not ready for 4.0 status, let alone 4.4/4.5 status. It hasn&#8217;t been properly tested and patched for those revision numbers.</p>
<p>I&#8217;m the founder and lead developer of a KDE based distro. Our distro is still using KDE 3.5 because many of our users practically hate KDE 4.x because of lack of usability/features &amp; serious crashes. KDE 4.x is bloated and performs poorly compared to KDE 3.5.x. We applaud the Trinity team for their efforts in maintaining KDE 3.5.x at least until KDE 4 is no longer performing like a late alpha/early beta. I&#8217;m not against change or progress, but change just for the sake of &#8220;progress&#8221; is an exercise in vanity, and changing version numbers does not make a project stable. Especially if the newer product simply cannot do what the former can do, or is many times less stable than the previous version! </p>
<p>Even though we are a small and very recent distro, we are now looking to see if there&#8217;s some way our 4 person dev team can help the Trinity project. I would encourage other dev teams look into doing the same thing until KDE actually releases a product worthy of normal use by Linux users.</p>
<p>KDE should pull KDE 4.x out of production and maintain/support KDE 3.5.x until KDE 4.x is truly a stable, feature-rich product that is actually ready to use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheBlackCat</title>
		<link>http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/comment-page-1/#comment-485</link>
		<dc:creator>TheBlackCat</dc:creator>
		<pubDate>Sun, 30 May 2010 16:29:19 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/#comment-485</guid>
		<description>So I guess it never occurred to you that the problem might be that you are using KDE 4.3, when KDE 4.4 is the current version and KDE 4.5 is just around the corner?  In 4.4 I only get plasma crashes when first loading buggy scripted widgets, and there were a lot of features in both 4.4 or 4.5.</description>
		<content:encoded><![CDATA[<p>So I guess it never occurred to you that the problem might be that you are using KDE 4.3, when KDE 4.4 is the current version and KDE 4.5 is just around the corner?  In 4.4 I only get plasma crashes when first loading buggy scripted widgets, and there were a lot of features in both 4.4 or 4.5.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pinotree</title>
		<link>http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/comment-page-1/#comment-482</link>
		<dc:creator>pinotree</dc:creator>
		<pubDate>Sun, 30 May 2010 10:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/#comment-482</guid>
		<description>&gt; What KDE3 applications are not ported to QT4 yet and how much effort would it take?

It depends also on you also; there are people whose normal KDE use involves applications that were ported to KDE4.
Do you still have kde3 application which you use?

&gt; When KDE4 was announced there were many promises e.g. platform independence.
&gt; Why aren’t the MAC OS X and Windows port stable yet

The fact that KDE4 is more platform independent than KDE3 does not imply it will compile,
work, and produce packages of itself without anybody doing the job.
There are some people working on the Windows port, but quite less on the Mac one.

&gt; and what still needs to be done there?

I guess you should ask to the kde-windows and kde-mac teams.

&gt; What can be done to improve the translation status of KDE4 applications?
&gt;  http://i18n.kde.org/stats/gui/trunk-kde4/team/

There were translations as well in KDE3, I don&#039;t see what it has to do with this blog...
Anyhow, back to your question: the way is always the same, ie contact and work with
the translation team of your language: http://i18n.kde.org/teams-list.php
(Note also the trunk statistics reflect the development version, which not all the teams
translate everyday; you might want to look at the &quot;stable&quot; statistics for the current
stable serie, ie KDE 4.4.x.)

&gt; What happened to Raptor?

Dunno.

&gt; When will Plasma be crash-free for normal use? KDE 4.6?

Note also kicker had &quot;normal use&quot; crashes, and a couple got fixed with quite late versions like KDE 3.5.10.

&gt; How can contributions to KDE4 be simplified? How to simple set a KDE4 built environment with TRUNK that “just works”?

Just follow the instructions on http.//techbase.kde.org ?</description>
		<content:encoded><![CDATA[<p>&gt; What KDE3 applications are not ported to QT4 yet and how much effort would it take?</p>
<p>It depends also on you also; there are people whose normal KDE use involves applications that were ported to KDE4.<br />
Do you still have kde3 application which you use?</p>
<p>&gt; When KDE4 was announced there were many promises e.g. platform independence.<br />
&gt; Why aren’t the MAC OS X and Windows port stable yet</p>
<p>The fact that KDE4 is more platform independent than KDE3 does not imply it will compile,<br />
work, and produce packages of itself without anybody doing the job.<br />
There are some people working on the Windows port, but quite less on the Mac one.</p>
<p>&gt; and what still needs to be done there?</p>
<p>I guess you should ask to the kde-windows and kde-mac teams.</p>
<p>&gt; What can be done to improve the translation status of KDE4 applications?<br />
&gt;  <a href="http://i18n.kde.org/stats/gui/trunk-kde4/team/" rel="nofollow">http://i18n.kde.org/stats/gui/trunk-kde4/team/</a></p>
<p>There were translations as well in KDE3, I don&#8217;t see what it has to do with this blog&#8230;<br />
Anyhow, back to your question: the way is always the same, ie contact and work with<br />
the translation team of your language: <a href="http://i18n.kde.org/teams-list.php" rel="nofollow">http://i18n.kde.org/teams-list.php</a><br />
(Note also the trunk statistics reflect the development version, which not all the teams<br />
translate everyday; you might want to look at the &#8220;stable&#8221; statistics for the current<br />
stable serie, ie KDE 4.4.x.)</p>
<p>&gt; What happened to Raptor?</p>
<p>Dunno.</p>
<p>&gt; When will Plasma be crash-free for normal use? KDE 4.6?</p>
<p>Note also kicker had &#8220;normal use&#8221; crashes, and a couple got fixed with quite late versions like KDE 3.5.10.</p>
<p>&gt; How can contributions to KDE4 be simplified? How to simple set a KDE4 built environment with TRUNK that “just works”?</p>
<p>Just follow the instructions on http.//techbase.kde.org ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Lashkevich</title>
		<link>http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/comment-page-1/#comment-481</link>
		<dc:creator>Michael Lashkevich</dc:creator>
		<pubDate>Sun, 30 May 2010 09:49:23 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/2010/05/trinity-and-the-challenges-of-continuing-kde-3/#comment-481</guid>
		<description>I think that KDE4 is still a development (not stable) project. Nearly every user interface feature, which is simple and transparent in KDE3.5, is difficult or not implemented in KDE4. I could attach here a huge list of absolutely necessary features that are not implemented in KDE4, but I want to be concise. It is very difficult to configure the desktop in KDE4, and it still crashes from time to time. The last version I tested is KDE4.3.5 and it is still MUCH WORSE than KDE3.5.

Look at the Mozilla team. Any feature of Firefox 1 is realized in Firefox 2 and any feature of Firefox 2 is realized in Firefox 3. It was an ethically wrong decision to issue KDE4.0, while you knew that it did not support EVERY feature of KDE3.5. Surely, you can force users to use KDE4 finally, but it is like a rape.</description>
		<content:encoded><![CDATA[<p>I think that KDE4 is still a development (not stable) project. Nearly every user interface feature, which is simple and transparent in KDE3.5, is difficult or not implemented in KDE4. I could attach here a huge list of absolutely necessary features that are not implemented in KDE4, but I want to be concise. It is very difficult to configure the desktop in KDE4, and it still crashes from time to time. The last version I tested is KDE4.3.5 and it is still MUCH WORSE than KDE3.5.</p>
<p>Look at the Mozilla team. Any feature of Firefox 1 is realized in Firefox 2 and any feature of Firefox 2 is realized in Firefox 3. It was an ethically wrong decision to issue KDE4.0, while you knew that it did not support EVERY feature of KDE3.5. Surely, you can force users to use KDE4 finally, but it is like a rape.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

