<?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: Thoughts on desktop Linux incompatibilities with iPhone and Android</title>
	<atom:link href="http://blog.cdleary.com/2008/09/thoughts-on-desktop-linux-incompatibilities-with-iphone-and-android/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cdleary.com/2008/09/thoughts-on-desktop-linux-incompatibilities-with-iphone-and-android/</link>
	<description>__author__ = &#039;Chris Leary&#039;</description>
	<lastBuildDate>Mon, 06 Sep 2010 19:31:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: stella</title>
		<link>http://blog.cdleary.com/2008/09/thoughts-on-desktop-linux-incompatibilities-with-iphone-and-android/comment-page-1/#comment-1113</link>
		<dc:creator>stella</dc:creator>
		<pubDate>Thu, 21 May 2009 09:08:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cdleary.com/?p=184#comment-1113</guid>
		<description>Exactly. More and more cases of rejected apps, because the &quot;duplicate&quot; Apple apps. What&#039;s that? Developers get screwed for their hard work. On this point, Google already made s statement: Anyone can sell his software on their marketplace. Nice posting, and so true.</description>
		<content:encoded><![CDATA[<p>Exactly. More and more cases of rejected apps, because the &#8220;duplicate&#8221; Apple apps. What&#8217;s that? Developers get screwed for their hard work. On this point, Google already made s statement: Anyone can sell his software on their marketplace. Nice posting, and so true.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Arvidson</title>
		<link>http://blog.cdleary.com/2008/09/thoughts-on-desktop-linux-incompatibilities-with-iphone-and-android/comment-page-1/#comment-75</link>
		<dc:creator>Mark Arvidson</dc:creator>
		<pubDate>Sun, 21 Sep 2008 14:29:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cdleary.com/?p=184#comment-75</guid>
		<description>Your article is dead on. Doing ANYTHING to interface with iTunes, either server, client or content is only reinforcing the growing monopoly that Apple is building.   Likewise goes for all other glitz and glamor of the iPhone.  The only long-term true option is displacement of the product with a FLOSS product solving the same problem space.  The best truly and completely FLOSS option is Openmoko (http://wiki.openmoko.org).  

Besides hype, the iPhone provides a tightly integrated, friendly interface, hiding the complexities of a mobile computer from the user.  This is an area where all other mobile devices have failed.  In order to be independently accepted by the community at large, the device must not be complex, regardless of functionality.  Most smart phones try to tout their capabilities with a complex, hard to navigate array of options.  This is a deterrent to non-tech users, who represent a large majority of the market.

The drawback to FLOSS developers scratching their own itch is that the iPhone scratches everyone else&#039;s itches too.</description>
		<content:encoded><![CDATA[<p>Your article is dead on. Doing ANYTHING to interface with iTunes, either server, client or content is only reinforcing the growing monopoly that Apple is building.   Likewise goes for all other glitz and glamor of the iPhone.  The only long-term true option is displacement of the product with a FLOSS product solving the same problem space.  The best truly and completely FLOSS option is Openmoko (<a href="http://wiki.openmoko.org" rel="nofollow">http://wiki.openmoko.org</a>).  </p>
<p>Besides hype, the iPhone provides a tightly integrated, friendly interface, hiding the complexities of a mobile computer from the user.  This is an area where all other mobile devices have failed.  In order to be independently accepted by the community at large, the device must not be complex, regardless of functionality.  Most smart phones try to tout their capabilities with a complex, hard to navigate array of options.  This is a deterrent to non-tech users, who represent a large majority of the market.</p>
<p>The drawback to FLOSS developers scratching their own itch is that the iPhone scratches everyone else&#8217;s itches too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: harnir</title>
		<link>http://blog.cdleary.com/2008/09/thoughts-on-desktop-linux-incompatibilities-with-iphone-and-android/comment-page-1/#comment-66</link>
		<dc:creator>harnir</dc:creator>
		<pubDate>Sat, 20 Sep 2008 19:05:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cdleary.com/?p=184#comment-66</guid>
		<description>How about OpenMoko and it&#039;s phone, Neo FreeRunner? It took off recently, and already some forks are popping up: OpnMokast - http://openmokast.org/, NeoPwn - http://www.neopwn.com/.

Yeah, maybe the software is in very eraly stage of development, and hardware is not cutting edge technology, but it&#039;s open. You can build on that and make the next version great. And no one will stop you for making support for it in your desktop OS.

http://wiki.openmoko.org/</description>
		<content:encoded><![CDATA[<p>How about OpenMoko and it&#8217;s phone, Neo FreeRunner? It took off recently, and already some forks are popping up: OpnMokast &#8211; <a href="http://openmokast.org/" rel="nofollow">http://openmokast.org/</a>, NeoPwn &#8211; <a href="http://www.neopwn.com/" rel="nofollow">http://www.neopwn.com/</a>.</p>
<p>Yeah, maybe the software is in very eraly stage of development, and hardware is not cutting edge technology, but it&#8217;s open. You can build on that and make the next version great. And no one will stop you for making support for it in your desktop OS.</p>
<p><a href="http://wiki.openmoko.org/" rel="nofollow">http://wiki.openmoko.org/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
