<?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: GNOME plans for the future</title>
	<atom:link href="http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/</link>
	<description>Just another GNOME Blogs weblog</description>
	<lastBuildDate>Mon, 23 Nov 2009 03:18:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Diego</title>
		<link>http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/comment-page-1/#comment-720</link>
		<dc:creator>Diego</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/#comment-720</guid>
		<description>I wouldn&#039;t say that KDE4 is not doing anything &quot;new&quot;. From that POV, you could say that gnome 2.0 was not doing anything &quot;new&quot; compared with gnome 1.x.&lt;p/&gt; KDE 4 is still a computer desktop environment, but it&#039;s a radical, &quot;revolutionary&quot; (as in: your old apps won&#039;t work, you&#039;ve to rewrite lots of code) change from kde 3.</description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t say that KDE4 is not doing anything &#8220;new&#8221;. From that POV, you could say that gnome 2.0 was not doing anything &#8220;new&#8221; compared with gnome 1.x.
<p /> KDE 4 is still a computer desktop environment, but it&#8217;s a radical, &#8220;revolutionary&#8221; (as in: your old apps won&#8217;t work, you&#8217;ve to rewrite lots of code) change from kde 3.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: knipknap</title>
		<link>http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/comment-page-1/#comment-721</link>
		<dc:creator>knipknap</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/#comment-721</guid>
		<description>IMO, GNOME has shifted away from the simplicity idea lately. This first showed by the inclusion of Evolution, which was way more &quot;bloated&quot; UI wise than other GNOME applications, Rhythmbox, and probably others too. Don&#039;t get me wrong, I believe that for GNOME&#039;s success shipping these more powerful applications was absolutely important at that time, and it has certainly helped it&#039;s adoption in enterprise environments.&lt;p/&gt;Yet, I would love to see innovative new solutions. For example, there are ideas to create a dead-simple tag based email application, instead of yet another tool that looks like all others.&lt;br/&gt;Also, Muine as a music player has a more granny compatible user interface than the iTunes clones. I would love to see a desktop that is built around such simplicity.</description>
		<content:encoded><![CDATA[<p>IMO, GNOME has shifted away from the simplicity idea lately. This first showed by the inclusion of Evolution, which was way more &#8220;bloated&#8221; UI wise than other GNOME applications, Rhythmbox, and probably others too. Don&#8217;t get me wrong, I believe that for GNOME&#8217;s success shipping these more powerful applications was absolutely important at that time, and it has certainly helped it&#8217;s adoption in enterprise environments.
<p />Yet, I would love to see innovative new solutions. For example, there are ideas to create a dead-simple tag based email application, instead of yet another tool that looks like all others.<br />Also, Muine as a music player has a more granny compatible user interface than the iTunes clones. I would love to see a desktop that is built around such simplicity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erich</title>
		<link>http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/comment-page-1/#comment-722</link>
		<dc:creator>Erich</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/#comment-722</guid>
		<description>You points about the need for a Gnome 3 are good. Gnome is nice as it is. I would however like to point something out.&lt;p/&gt;It&#039;s mostly C. While that is nice (it&#039;s efficient and the core developers really know how to handle it) it scares away some potential contributors. Contributing in C++ or some higher level language (Ruby for instance, it eats Python for breakfast) being *standardly* included possibility (if your application will require installing &quot;extra&quot; -mm libraries it will stay 2nd class citizen because many distros etc want to keep things small) would drive in more people to develop Gnome applications. &lt;p/&gt;You have to keep in mind that many people are taught nowadays higher level languages only. They can be good programmers but having to learn the ways of C is an unwanted extra burden for some. At least C++ would be an improvement. It can be efficient too, both in execution and to develop. Better yet, Ruby (or Python if you really MUST) could be a killer. &lt;p/&gt;Myself I have been thinking about revamping completely the icon selection (for files and runnable items on the gnome-panel) because it has HORRIBLE usability. (Why on earth can&#039;t I just select one of the THEMES installed and then the icon, why do I have to know about directory paths?!!?) I&#039;m not quite willing to write any C however. I could but it&#039;s too time consuming and loathsome when I&#039;m usually programming in Ruby or Java. I&#039;ve been thinking the same about Dia. Hopping in and revising it pretty much completely. It seems horrible as well :-)&lt;p/&gt;So there MIGHT actually be &quot;need&quot; for Gnome 3.0. Not becauce of features but because of refactoring into a position where contributions in 1 great higher level language would be wanted also into the core&lt;br/&gt;</description>
		<content:encoded><![CDATA[<p>You points about the need for a Gnome 3 are good. Gnome is nice as it is. I would however like to point something out.
<p />It&#8217;s mostly C. While that is nice (it&#8217;s efficient and the core developers really know how to handle it) it scares away some potential contributors. Contributing in C++ or some higher level language (Ruby for instance, it eats Python for breakfast) being *standardly* included possibility (if your application will require installing &#8220;extra&#8221; -mm libraries it will stay 2nd class citizen because many distros etc want to keep things small) would drive in more people to develop Gnome applications.
<p />You have to keep in mind that many people are taught nowadays higher level languages only. They can be good programmers but having to learn the ways of C is an unwanted extra burden for some. At least C++ would be an improvement. It can be efficient too, both in execution and to develop. Better yet, Ruby (or Python if you really MUST) could be a killer.
<p />Myself I have been thinking about revamping completely the icon selection (for files and runnable items on the gnome-panel) because it has HORRIBLE usability. (Why on earth can&#8217;t I just select one of the THEMES installed and then the icon, why do I have to know about directory paths?!!?) I&#8217;m not quite willing to write any C however. I could but it&#8217;s too time consuming and loathsome when I&#8217;m usually programming in Ruby or Java. I&#8217;ve been thinking the same about Dia. Hopping in and revising it pretty much completely. It seems horrible as well <img src='http://blogs.gnome.org/uraeus/wp-content/mu-plugins/tango-smilies/tango/face-smile.png' alt=':-)' class='wp-smiley' />
<p />So there MIGHT actually be &#8220;need&#8221; for Gnome 3.0. Not becauce of features but because of refactoring into a position where contributions in 1 great higher level language would be wanted also into the core</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: superstoned</title>
		<link>http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/comment-page-1/#comment-723</link>
		<dc:creator>superstoned</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/#comment-723</guid>
		<description>@knipknap: what&#039;s the use of simplicity? it helps ppl to get up and running faster, touché. but that&#039;s only helping what, week of the whole 50 years one uses a computer? i&#039;d take an advanced but a bit harder-to-learn interface over a totally dumbed down interface which doesn&#039;t allow anyone to work efficiently with it. Ok, feature overkill lowers efficiency. but you can&#039;t dumb down and gain efficiency forever. better THINK more about how to integrate the features. imho all those simplicity isn&#039;t worth anything. more an excuse for &#039;we don&#039;t have time to implement the features&#039; or, in other words &#039;sorry, we&#039;re behind the competition. but look how usable it is!&#039;.</description>
		<content:encoded><![CDATA[<p>@<a href="http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/#comment-725">knipknap</a>: what&#8217;s the use of simplicity? it helps ppl to get up and running faster, touché. but that&#8217;s only helping what, week of the whole 50 years one uses a computer? i&#8217;d take an advanced but a bit harder-to-learn interface over a totally dumbed down interface which doesn&#8217;t allow anyone to work efficiently with it. Ok, feature overkill lowers efficiency. but you can&#8217;t dumb down and gain efficiency forever. better THINK more about how to integrate the features. imho all those simplicity isn&#8217;t worth anything. more an excuse for &#8216;we don&#8217;t have time to implement the features&#8217; or, in other words &#8217;sorry, we&#8217;re behind the competition. but look how usable it is!&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: byteframe</title>
		<link>http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/comment-page-1/#comment-724</link>
		<dc:creator>byteframe</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/#comment-724</guid>
		<description>Easy, Gnome 3 should have an entire revamped build system thing. It should be as easy to build and install as KDE. I would think something like this would require huge changes, and so calling it Gnome 3 would be good. Couple that with out of the box support for all that funky opengl window manager shit and I&#039;d say a major release like that would be warrented.</description>
		<content:encoded><![CDATA[<p>Easy, Gnome 3 should have an entire revamped build system thing. It should be as easy to build and install as KDE. I would think something like this would require huge changes, and so calling it Gnome 3 would be good. Couple that with out of the box support for all that funky opengl window manager shit and I&#8217;d say a major release like that would be warrented.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: knipknap</title>
		<link>http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/comment-page-1/#comment-725</link>
		<dc:creator>knipknap</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/#comment-725</guid>
		<description>superstoned: Simple applications do not need to have less features. In fact, I found that by adding additional &quot;smart&quot; features you can often get rid of UI bloat.&lt;p/&gt;For example, in OpenOffice they could add a &quot;File -&gt; Save a copy...&quot; menu item and get rid of the &quot;Save as...&quot;, &quot;Export...&quot; and &quot;Export as PDF...&quot; menu items all at once, since they all do the same thing for a subset of document types. After the change you could in fact perform the same action on more document types than before.&lt;p/&gt;Same thing goes for tag based email.</description>
		<content:encoded><![CDATA[<p>superstoned: Simple applications do not need to have less features. In fact, I found that by adding additional &#8220;smart&#8221; features you can often get rid of UI bloat.
<p />For example, in OpenOffice they could add a &#8220;File -&gt; Save a copy&#8230;&#8221; menu item and get rid of the &#8220;Save as&#8230;&#8221;, &#8220;Export&#8230;&#8221; and &#8220;Export as PDF&#8230;&#8221; menu items all at once, since they all do the same thing for a subset of document types. After the change you could in fact perform the same action on more document types than before.
<p />Same thing goes for tag based email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy Schestowitz</title>
		<link>http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/comment-page-1/#comment-726</link>
		<dc:creator>Roy Schestowitz</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/#comment-726</guid>
		<description>Thom planted the flamebait. No need to feed the trolls.</description>
		<content:encoded><![CDATA[<p>Thom planted the flamebait. No need to feed the trolls.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Acacio</title>
		<link>http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/comment-page-1/#comment-727</link>
		<dc:creator>Mark Acacio</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/#comment-727</guid>
		<description>Who is this &quot;thom&quot;? Who cares about what that guy thinks? Why am I wasting my time even reading something related to that guy&#039;s opinion??</description>
		<content:encoded><![CDATA[<p>Who is this &#8220;thom&#8221;? Who cares about what that guy thinks? Why am I wasting my time even reading something related to that guy&#8217;s opinion??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alex</title>
		<link>http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/comment-page-1/#comment-728</link>
		<dc:creator>alex</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/#comment-728</guid>
		<description>Who is this &quot;Mark Acacio&quot;? Who cares about what that guy thinks? Why am I wasting my time even reading something related to that guy&#039;s opinion??</description>
		<content:encoded><![CDATA[<p>Who is this &#8220;Mark Acacio&#8221;? Who cares about what that guy thinks? Why am I wasting my time even reading something related to that guy&#8217;s opinion??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Me</title>
		<link>http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/comment-page-1/#comment-729</link>
		<dc:creator>Me</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/12/31/gnome-plans-for-the-future/#comment-729</guid>
		<description>Who is this &quot;alex&quot;? Who cares about what that guy thinks? Why am I wasting my time even reading something related to that guy&#039;s opinion??&lt;p/&gt;</description>
		<content:encoded><![CDATA[<p>Who is this &#8220;alex&#8221;? Who cares about what that guy thinks? Why am I wasting my time even reading something related to that guy&#8217;s opinion??
<p />
]]></content:encoded>
	</item>
</channel>
</rss>
