<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: The future of Sugar</title>
	<atom:link href="http://morgancollett.wordpress.com/2008/05/16/the-future-of-sugar/feed/" rel="self" type="application/rss+xml" />
	<link>http://morgancollett.wordpress.com/2008/05/16/the-future-of-sugar/</link>
	<description>Thoughts of an Ubunut</description>
	<lastBuildDate>Wed, 09 Sep 2009 23:30:17 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Austin</title>
		<link>http://morgancollett.wordpress.com/2008/05/16/the-future-of-sugar/#comment-1054</link>
		<dc:creator>Austin</dc:creator>
		<pubDate>Mon, 19 May 2008 00:47:31 +0000</pubDate>
		<guid isPermaLink="false">http://morgancollett.wordpress.com/?p=80#comment-1054</guid>
		<description>Just on the windows platform compatibility stuff, why not put a small 1% effort into the Wine project?  Many of the windows functions are already implemented and the ones that are needed can be done on a case by case basis within a framework that already works for people?  Seems to me that saying &quot;it needs windows&quot; is a strange way of saying that we aren&#039;t serious about OSS development and don&#039;t understand how it works.</description>
		<content:encoded><![CDATA[<p>Just on the windows platform compatibility stuff, why not put a small 1% effort into the Wine project?  Many of the windows functions are already implemented and the ones that are needed can be done on a case by case basis within a framework that already works for people?  Seems to me that saying &#8220;it needs windows&#8221; is a strange way of saying that we aren&#8217;t serious about OSS development and don&#8217;t understand how it works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guillermo</title>
		<link>http://morgancollett.wordpress.com/2008/05/16/the-future-of-sugar/#comment-1053</link>
		<dc:creator>Guillermo</dc:creator>
		<pubDate>Sat, 17 May 2008 02:36:31 +0000</pubDate>
		<guid isPermaLink="false">http://morgancollett.wordpress.com/?p=80#comment-1053</guid>
		<description>I agree, Sugar introduced a new paradigm for user interfaces that can&#039;t be ignored. Connecting users within a mesh through applications, making every application capable of being shared. I&#039;m glad you will continue to work on the project, and this new directions looks promising. I look forward to develop applications for it.

Good job.</description>
		<content:encoded><![CDATA[<p>I agree, Sugar introduced a new paradigm for user interfaces that can&#8217;t be ignored. Connecting users within a mesh through applications, making every application capable of being shared. I&#8217;m glad you will continue to work on the project, and this new directions looks promising. I look forward to develop applications for it.</p>
<p>Good job.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Free Software Stuff &#187; Blog Archive &#187; Problemi u zemlji malih zelenih (laptopa)</title>
		<link>http://morgancollett.wordpress.com/2008/05/16/the-future-of-sugar/#comment-1052</link>
		<dc:creator>Free Software Stuff &#187; Blog Archive &#187; Problemi u zemlji malih zelenih (laptopa)</dc:creator>
		<pubDate>Sat, 17 May 2008 00:34:41 +0000</pubDate>
		<guid isPermaLink="false">http://morgancollett.wordpress.com/?p=80#comment-1052</guid>
		<description>[...] što je sa Sugarom, inovativnim sučeljem OLPC-a? Sugar neće umrijeti niti bačen u prvi plan. Ekipa iz OLPC-a uvjerava nas da se na tome radi punom parom i da [...]</description>
		<content:encoded><![CDATA[<p>[...] što je sa Sugarom, inovativnim sučeljem OLPC-a? Sugar neće umrijeti niti bačen u prvi plan. Ekipa iz OLPC-a uvjerava nas da se na tome radi punom parom i da [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sameer Verma</title>
		<link>http://morgancollett.wordpress.com/2008/05/16/the-future-of-sugar/#comment-1051</link>
		<dc:creator>Sameer Verma</dc:creator>
		<pubDate>Fri, 16 May 2008 21:38:47 +0000</pubDate>
		<guid isPermaLink="false">http://morgancollett.wordpress.com/?p=80#comment-1051</guid>
		<description>I agree that we have to put efforts first. No questions there. 

However, keep in mind that a superior technology in itself is not enough to improve adoption. There is the classic Betamax vs. VHS case: http://en.wikipedia.org/wiki/Betamax#The_legacy_of_Betamax  What drives adoption isn&#039;t so much the real technology, as it is its perception. We have to make sure that the perception that end users (children, parents, teachers, etc.) hold in their minds leans towards Sugar as being the significant value-add and not a weird thing that isn&#039;t quite like Windows. 

A wider exposure to Sugar will work in its favor (massive exposure and feedback), and by decoupling Sugar from its Fedora innards, we can reach a lot more children. There are many schools in not so poor neighborhoods around the world that already have computer labs. They will now be able to reap the benefits of Sugar. Imagine being able to run Sugar via LTSP-type terminal services across hundreds of computers!

Its a good thing that such a reshuffling of the stack has led to a shift in scale for Sugar. I sincerely hope its for the best.</description>
		<content:encoded><![CDATA[<p>I agree that we have to put efforts first. No questions there. </p>
<p>However, keep in mind that a superior technology in itself is not enough to improve adoption. There is the classic Betamax vs. VHS case: <a href="http://en.wikipedia.org/wiki/Betamax#The_legacy_of_Betamax" rel="nofollow">http://en.wikipedia.org/wiki/Betamax#The_legacy_of_Betamax</a>  What drives adoption isn&#8217;t so much the real technology, as it is its perception. We have to make sure that the perception that end users (children, parents, teachers, etc.) hold in their minds leans towards Sugar as being the significant value-add and not a weird thing that isn&#8217;t quite like Windows. </p>
<p>A wider exposure to Sugar will work in its favor (massive exposure and feedback), and by decoupling Sugar from its Fedora innards, we can reach a lot more children. There are many schools in not so poor neighborhoods around the world that already have computer labs. They will now be able to reap the benefits of Sugar. Imagine being able to run Sugar via LTSP-type terminal services across hundreds of computers!</p>
<p>Its a good thing that such a reshuffling of the stack has led to a shift in scale for Sugar. I sincerely hope its for the best.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco Pesenti Gritti</title>
		<link>http://morgancollett.wordpress.com/2008/05/16/the-future-of-sugar/#comment-1050</link>
		<dc:creator>Marco Pesenti Gritti</dc:creator>
		<pubDate>Fri, 16 May 2008 17:20:08 +0000</pubDate>
		<guid isPermaLink="false">http://morgancollett.wordpress.com/?p=80#comment-1050</guid>
		<description>Excellent post Morgan. And +1 to bryan!</description>
		<content:encoded><![CDATA[<p>Excellent post Morgan. And +1 to bryan!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bryan berry</title>
		<link>http://morgancollett.wordpress.com/2008/05/16/the-future-of-sugar/#comment-1049</link>
		<dc:creator>bryan berry</dc:creator>
		<pubDate>Fri, 16 May 2008 15:33:13 +0000</pubDate>
		<guid isPermaLink="false">http://morgancollett.wordpress.com/?p=80#comment-1049</guid>
		<description>Well said Morgan. Let&#039;s make this happen and stop having meta-discussions about constructionist education. Let&#039;s actually do ti.</description>
		<content:encoded><![CDATA[<p>Well said Morgan. Let&#8217;s make this happen and stop having meta-discussions about constructionist education. Let&#8217;s actually do ti.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
