<?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: the genius of Steve Jobs: he makes you want the lock-in</title>
	<atom:link href="http://benlog.com/articles/2010/04/29/the-genius-of-steve-jobs-he-makes-you-want-the-lock-in/feed/" rel="self" type="application/rss+xml" />
	<link>http://benlog.com/articles/2010/04/29/the-genius-of-steve-jobs-he-makes-you-want-the-lock-in/</link>
	<description>security, privacy, transparency.</description>
	<lastBuildDate>Mon, 30 Jan 2012 20:03:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: The Openness of Flash &#187; pixxid</title>
		<link>http://benlog.com/articles/2010/04/29/the-genius-of-steve-jobs-he-makes-you-want-the-lock-in/comment-page-1/#comment-638611</link>
		<dc:creator>The Openness of Flash &#187; pixxid</dc:creator>
		<pubDate>Thu, 31 Mar 2011 10:24:09 +0000</pubDate>
		<guid isPermaLink="false">http://benlog.com/?p=1197#comment-638611</guid>
		<description>[...] to Steve Jobs&#8217; Thoughts on Flash post, there&#8217;s been a whole new flurry of posts on the subject of flash vs html5, this time with some focus on the issue of openness, since Steve [...]</description>
		<content:encoded><![CDATA[<p>[...] to Steve Jobs&#8217; Thoughts on Flash post, there&#8217;s been a whole new flurry of posts on the subject of flash vs html5, this time with some focus on the issue of openness, since Steve [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://benlog.com/articles/2010/04/29/the-genius-of-steve-jobs-he-makes-you-want-the-lock-in/comment-page-1/#comment-631543</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Mon, 03 May 2010 18:50:53 +0000</pubDate>
		<guid isPermaLink="false">http://benlog.com/?p=1197#comment-631543</guid>
		<description>Also note the lack of memory card readers on the media devices </description>
		<content:encoded><![CDATA[<p>Also note the lack of memory card readers on the media devices</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Herring</title>
		<link>http://benlog.com/articles/2010/04/29/the-genius-of-steve-jobs-he-makes-you-want-the-lock-in/comment-page-1/#comment-631540</link>
		<dc:creator>Nathan Herring</dc:creator>
		<pubDate>Fri, 30 Apr 2010 20:56:55 +0000</pubDate>
		<guid isPermaLink="false">http://benlog.com/?p=1197#comment-631540</guid>
		<description>Applications written with a cross-platform development tool _are_ starting with a handicap, and its a handicap that is usually directly related to the height of both of the platforms&#039; framework stacks. This makes a tremendous difference when using a cross-platform UI stack (since UI stacks tend to be large and non-homogenous), vs. a bare computing or networking stack. Having &quot;native&quot; UI code and cross-platform business logic seems like a fine way of not watering down the platform, and yet this is not allowed.

I can, however, still fathom a reason for maintaining (at least) a ban on the (UI) cross-platform libraries use -- even if they were to hold these apps up to the &quot;high&quot; standards of native (UI) frameworks, they&#039;d still be responsible for repeatedly shooting down applications for being &quot;tacky&quot;. The cost of dealing with those submissions and their probably repeated denials is something they can easily obviate with a stroke of their legal pen.

My only suspicion is that only Apple will decide whether or not to enforce these clauses, and that developers will continue to submit products that don&#039;t meet the criteria of the license, and for apps/developers deemed to be helping the platform, Apple may look the other way. </description>
		<content:encoded><![CDATA[<p>Applications written with a cross-platform development tool _are_ starting with a handicap, and its a handicap that is usually directly related to the height of both of the platforms&#8217; framework stacks. This makes a tremendous difference when using a cross-platform UI stack (since UI stacks tend to be large and non-homogenous), vs. a bare computing or networking stack. Having &#8220;native&#8221; UI code and cross-platform business logic seems like a fine way of not watering down the platform, and yet this is not allowed.</p>
<p>I can, however, still fathom a reason for maintaining (at least) a ban on the (UI) cross-platform libraries use &#8212; even if they were to hold these apps up to the &#8220;high&#8221; standards of native (UI) frameworks, they&#8217;d still be responsible for repeatedly shooting down applications for being &#8220;tacky&#8221;. The cost of dealing with those submissions and their probably repeated denials is something they can easily obviate with a stroke of their legal pen.</p>
<p>My only suspicion is that only Apple will decide whether or not to enforce these clauses, and that developers will continue to submit products that don&#8217;t meet the criteria of the license, and for apps/developers deemed to be helping the platform, Apple may look the other way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cris</title>
		<link>http://benlog.com/articles/2010/04/29/the-genius-of-steve-jobs-he-makes-you-want-the-lock-in/comment-page-1/#comment-631539</link>
		<dc:creator>Cris</dc:creator>
		<pubDate>Fri, 30 Apr 2010 12:30:35 +0000</pubDate>
		<guid isPermaLink="false">http://benlog.com/?p=1197#comment-631539</guid>
		<description>All I can say as an open source developer is, ahaha suck it down app store developers. Dance with the devil, this is what happens. It&#039;s not like it wasn&#039;t patently obvious this was coming. </description>
		<content:encoded><![CDATA[<p>All I can say as an open source developer is, ahaha suck it down app store developers. Dance with the devil, this is what happens. It&#8217;s not like it wasn&#8217;t patently obvious this was coming.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander Fritze</title>
		<link>http://benlog.com/articles/2010/04/29/the-genius-of-steve-jobs-he-makes-you-want-the-lock-in/comment-page-1/#comment-631538</link>
		<dc:creator>Alexander Fritze</dc:creator>
		<pubDate>Fri, 30 Apr 2010 07:49:10 +0000</pubDate>
		<guid isPermaLink="false">http://benlog.com/?p=1197#comment-631538</guid>
		<description>the genius of steve jobs </description>
		<content:encoded><![CDATA[<p>the genius of steve jobs</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Adida</title>
		<link>http://benlog.com/articles/2010/04/29/the-genius-of-steve-jobs-he-makes-you-want-the-lock-in/comment-page-1/#comment-631535</link>
		<dc:creator>Ben Adida</dc:creator>
		<pubDate>Thu, 29 Apr 2010 19:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://benlog.com/?p=1197#comment-631535</guid>
		<description>If Apple introduces incompatible changes, I don&#039;t see how they would have to cater to Adobe anymore than to individual developers who would need to make changes to their native apps, too. And again, Apple can always yank those apps out if they are not upgraded past a certain point. Your point is by far the most valid technically of the set, but it&#039;s still not the root issue, I don&#039;t think. </description>
		<content:encoded><![CDATA[<p>If Apple introduces incompatible changes, I don&#8217;t see how they would have to cater to Adobe anymore than to individual developers who would need to make changes to their native apps, too. And again, Apple can always yank those apps out if they are not upgraded past a certain point. Your point is by far the most valid technically of the set, but it&#8217;s still not the root issue, I don&#8217;t think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Levesque</title>
		<link>http://benlog.com/articles/2010/04/29/the-genius-of-steve-jobs-he-makes-you-want-the-lock-in/comment-page-1/#comment-631534</link>
		<dc:creator>Ian Levesque</dc:creator>
		<pubDate>Thu, 29 Apr 2010 19:11:36 +0000</pubDate>
		<guid isPermaLink="false">http://benlog.com/?p=1197#comment-631534</guid>
		<description>&quot;Apple already has a mechanism to control for app quality: they can reject any app for any reason. So why add this additional level of control? Why automatically reject an app that happens to be originally built using Adobe’s cross-compiler, even if that app is good?&quot;

You addressed the first part of Job&#039;s statement but not the second (&quot;and hinders the enhancement and progress of the platform&quot;).  Once a good application is out in the wild, users will use it, depend on it, and make decisions about upgrades based upon its compatibility.  Apple has made many sweeping changes and enhancements to its SDK since it was originally released, and Adobe doesn&#039;t have a great track record keeping up with even the Mac (Core Image in Photoshop? Someday?), which moves much slower than the iPhone does. A large portion of developers will have to wait for Adobe to add new platform capabilities, and that does hurt the iPhone platform.  The need for Apple to cater to previously &quot;good&quot; Flash applications would become a hinderance to the progress of the platform. </description>
		<content:encoded><![CDATA[<p>&#8220;Apple already has a mechanism to control for app quality: they can reject any app for any reason. So why add this additional level of control? Why automatically reject an app that happens to be originally built using Adobe’s cross-compiler, even if that app is good?&#8221;</p>
<p>You addressed the first part of Job&#8217;s statement but not the second (&#8220;and hinders the enhancement and progress of the platform&#8221;).  Once a good application is out in the wild, users will use it, depend on it, and make decisions about upgrades based upon its compatibility.  Apple has made many sweeping changes and enhancements to its SDK since it was originally released, and Adobe doesn&#8217;t have a great track record keeping up with even the Mac (Core Image in Photoshop? Someday?), which moves much slower than the iPhone does. A large portion of developers will have to wait for Adobe to add new platform capabilities, and that does hurt the iPhone platform.  The need for Apple to cater to previously &#8220;good&#8221; Flash applications would become a hinderance to the progress of the platform.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

