<?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"
	>
<channel>
	<title>Comments for Neil Mix</title>
	<atom:link href="http://www.neilmix.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.neilmix.com</link>
	<description></description>
	<pubDate>Fri, 12 Mar 2010 02:44:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>Comment on Tablet Prediction by David Lowe</title>
		<link>http://www.neilmix.com/2010/01/23/tablet-prediction/#comment-213</link>
		<dc:creator>David Lowe</dc:creator>
		<pubDate>Wed, 27 Jan 2010 22:35:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.neilmix.com/?p=76#comment-213</guid>
		<description>Rats, no handwriting recognition. I agree, this makes it DOA for me personally.

Maybe it's time to resurrect the chorded (one-handed) keyboard for multi-touch screens? That's a different approach to the problem... http://en.wikipedia.org/wiki/Chorded_keyboard

(FWIW, I had a chorded keyboard for some time, and could type reasonably quickly with it. But the first time I tried coding in C with it, I gave up -- the semicolon was a two-step chord!)</description>
		<content:encoded><![CDATA[<p>Rats, no handwriting recognition. I agree, this makes it DOA for me personally.</p>
<p>Maybe it&#8217;s time to resurrect the chorded (one-handed) keyboard for multi-touch screens? That&#8217;s a different approach to the problem&#8230; <a href="http://en.wikipedia.org/wiki/Chorded_keyboard" rel="nofollow">http://en.wikipedia.org/wiki/Chorded_keyboard</a></p>
<p>(FWIW, I had a chorded keyboard for some time, and could type reasonably quickly with it. But the first time I tried coding in C with it, I gave up &#8212; the semicolon was a two-step chord!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Threading in JavaScript 1.7 by iresha</title>
		<link>http://www.neilmix.com/2007/02/07/threading-in-javascript-17/#comment-212</link>
		<dc:creator>iresha</dc:creator>
		<pubDate>Fri, 18 Dec 2009 01:15:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.neilmix.com/2007/09/09/threading-in-javascript-17/#comment-212</guid>
		<description>javascript multi-threading doesn't have to be a pointless exercise. Here is a fantastic example.

http://codediaries.blogspot.com/2009/12/real-javascript-multithreading-using.html</description>
		<content:encoded><![CDATA[<p>javascript multi-threading doesn&#8217;t have to be a pointless exercise. Here is a fantastic example.</p>
<p><a href="http://codediaries.blogspot.com/2009/12/real-javascript-multithreading-using.html" rel="nofollow">http://codediaries.blogspot.com/2009/12/real-javascript-multithreading-using.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Software on the shelf by Andy</title>
		<link>http://www.neilmix.com/2009/11/20/software-on-the-shelf/#comment-211</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Fri, 04 Dec 2009 20:07:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.neilmix.com/?p=72#comment-211</guid>
		<description>"I kept approaching implementation with a sense of urgency framed by the Internet, and my approach didn’t fit in with the rest of the team."

I hadn't considered the team's background on the overall sense of project urgency. That was interesting, thanks.</description>
		<content:encoded><![CDATA[<p>&#8220;I kept approaching implementation with a sense of urgency framed by the Internet, and my approach didn’t fit in with the rest of the team.&#8221;</p>
<p>I hadn&#8217;t considered the team&#8217;s background on the overall sense of project urgency. That was interesting, thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on It takes guts to do that by Matt Martel</title>
		<link>http://www.neilmix.com/2009/11/12/it-takes-guts-to-do-that/#comment-210</link>
		<dc:creator>Matt Martel</dc:creator>
		<pubDate>Sat, 21 Nov 2009 02:55:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.neilmix.com/?p=68#comment-210</guid>
		<description>Absolutely agree. As you say, Joe voted with his feet. More power to him. Rather see that than continued complaining from folks on the sidelines, ones without a stake in the game.</description>
		<content:encoded><![CDATA[<p>Absolutely agree. As you say, Joe voted with his feet. More power to him. Rather see that than continued complaining from folks on the sidelines, ones without a stake in the game.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Solve the right problem by Vincent Roman</title>
		<link>http://www.neilmix.com/2009/11/15/solve-the-right-problem/#comment-209</link>
		<dc:creator>Vincent Roman</dc:creator>
		<pubDate>Mon, 16 Nov 2009 17:41:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.neilmix.com/?p=70#comment-209</guid>
		<description>Greta post and right on the money.</description>
		<content:encoded><![CDATA[<p>Greta post and right on the money.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Please stop whining about App Store review by Neil</title>
		<link>http://www.neilmix.com/2009/11/11/please-stop-whining-about-app-store-review/#comment-208</link>
		<dc:creator>Neil</dc:creator>
		<pubDate>Thu, 12 Nov 2009 16:39:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.neilmix.com/?p=67#comment-208</guid>
		<description>@Chris: you're right -- over time, developers may vote with their feet (like Joe did) and force Apple's hand.  Until that happens, what's going to cause Apple to change?  Nothing.

@Joe: No point in comparing?  I couldn't disagree more.  Let's compare Apple's system with *all* previous systems including the web and the desktop, and let's see which ones fare the best.  Those who ignore history are doomed to repeat it, right?  As for  the best possible system -- from who's perspective?  My whole point is the the review process isn't developer friendly, but that's irrelevant as long as it's not hurting Apple's product and the end consumer.  So what's best for the end consumer?  Is the "wild west web" with no single distribution point, no standards of conduct, and no consumer recourse really best for consumers?  I'm not so quick to jump on that bandwagon.  Same goes for the desktop.</description>
		<content:encoded><![CDATA[<p>@Chris: you&#8217;re right &#8212; over time, developers may vote with their feet (like Joe did) and force Apple&#8217;s hand.  Until that happens, what&#8217;s going to cause Apple to change?  Nothing.</p>
<p>@Joe: No point in comparing?  I couldn&#8217;t disagree more.  Let&#8217;s compare Apple&#8217;s system with *all* previous systems including the web and the desktop, and let&#8217;s see which ones fare the best.  Those who ignore history are doomed to repeat it, right?  As for  the best possible system &#8212; from who&#8217;s perspective?  My whole point is the the review process isn&#8217;t developer friendly, but that&#8217;s irrelevant as long as it&#8217;s not hurting Apple&#8217;s product and the end consumer.  So what&#8217;s best for the end consumer?  Is the &#8220;wild west web&#8221; with no single distribution point, no standards of conduct, and no consumer recourse really best for consumers?  I&#8217;m not so quick to jump on that bandwagon.  Same goes for the desktop.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Please stop whining about App Store review by Joe Hewitt</title>
		<link>http://www.neilmix.com/2009/11/11/please-stop-whining-about-app-store-review/#comment-207</link>
		<dc:creator>Joe Hewitt</dc:creator>
		<pubDate>Thu, 12 Nov 2009 11:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.neilmix.com/?p=67#comment-207</guid>
		<description>I see no point in making comparisons to less than ideal systems of the past.  Let's imagine what the best possible system is and compare against that.  Yes, Apple's approval process is far easier than, say, getting approval for a Nintendo or Playstation game.  That doesn't mean it can't be improved.</description>
		<content:encoded><![CDATA[<p>I see no point in making comparisons to less than ideal systems of the past.  Let&#8217;s imagine what the best possible system is and compare against that.  Yes, Apple&#8217;s approval process is far easier than, say, getting approval for a Nintendo or Playstation game.  That doesn&#8217;t mean it can&#8217;t be improved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Please stop whining about App Store review by Chris Doherty</title>
		<link>http://www.neilmix.com/2009/11/11/please-stop-whining-about-app-store-review/#comment-206</link>
		<dc:creator>Chris Doherty</dc:creator>
		<pubDate>Thu, 12 Nov 2009 05:14:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.neilmix.com/?p=67#comment-206</guid>
		<description>"name the platforms for which indy developers were writing apps prior to the App Store's existence"

Blackberry and the Danger Sidekick? I believe the former was all user-installed, and the Danger "review process" was just technical (making sure your app didn't kill the backend service) and marking adult apps appropriately. None of this "duplicates an existing app's functionality" or "you can load the Kama Sutra, therefore your e-book reader is inappropriate" nonsense.

I would never expect to see *users* leave the iPhone--they don't care, they don't usually know about apps that aren't available. But I'd expect developers over time to think twice before putting significant time and effort (and hence money) writing an iPhone app without knowing whether they'll be able to sell it.</description>
		<content:encoded><![CDATA[<p>&#8220;name the platforms for which indy developers were writing apps prior to the App Store&#8217;s existence&#8221;</p>
<p>Blackberry and the Danger Sidekick? I believe the former was all user-installed, and the Danger &#8220;review process&#8221; was just technical (making sure your app didn&#8217;t kill the backend service) and marking adult apps appropriately. None of this &#8220;duplicates an existing app&#8217;s functionality&#8221; or &#8220;you can load the Kama Sutra, therefore your e-book reader is inappropriate&#8221; nonsense.</p>
<p>I would never expect to see *users* leave the iPhone&#8211;they don&#8217;t care, they don&#8217;t usually know about apps that aren&#8217;t available. But I&#8217;d expect developers over time to think twice before putting significant time and effort (and hence money) writing an iPhone app without knowing whether they&#8217;ll be able to sell it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Problem of Trust by Donny Viszneki</title>
		<link>http://www.neilmix.com/2009/05/04/the-problem-of-trust/#comment-204</link>
		<dc:creator>Donny Viszneki</dc:creator>
		<pubDate>Tue, 06 Oct 2009 13:49:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.neilmix.com/?p=59#comment-204</guid>
		<description>You want to talk about an SSL usability problem? Almost no SSL technology I've used has a comfortable user interface accepting known-to-be-compromised SSL certs. You either have to lump them in with the trusted certs, or reject them entirely.</description>
		<content:encoded><![CDATA[<p>You want to talk about an SSL usability problem? Almost no SSL technology I&#8217;ve used has a comfortable user interface accepting known-to-be-compromised SSL certs. You either have to lump them in with the trusted certs, or reject them entirely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Redacted?!? by Peter Edstrom</title>
		<link>http://www.neilmix.com/2009/08/22/redacted/#comment-203</link>
		<dc:creator>Peter Edstrom</dc:creator>
		<pubDate>Sun, 23 Aug 2009 02:00:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.neilmix.com/?p=65#comment-203</guid>
		<description>I'd agree, the whole thing stinks. 

On one hand, I sortof agree with Apple in that it alters the way voicemail and sms work. But only if you can turn a blind eye to the fact that it is a different phone number than your iPhone number, and that voicemail and sms continue to work unchanged. It's just that contacts might cease to use the iPhone number in favor of the gVoice number. There aren't any hacks of the iPhone native apps in any way.

What I think it'll come down to is wether or not the iPhone is considered a "product" or is considered a computer. If it's a general-purpose computer, then Apple will need to back down. They obviously can't restrict applications in OS X, and probably shouldn't be on the iPhone either.</description>
		<content:encoded><![CDATA[<p>I&#8217;d agree, the whole thing stinks. </p>
<p>On one hand, I sortof agree with Apple in that it alters the way voicemail and sms work. But only if you can turn a blind eye to the fact that it is a different phone number than your iPhone number, and that voicemail and sms continue to work unchanged. It&#8217;s just that contacts might cease to use the iPhone number in favor of the gVoice number. There aren&#8217;t any hacks of the iPhone native apps in any way.</p>
<p>What I think it&#8217;ll come down to is wether or not the iPhone is considered a &#8220;product&#8221; or is considered a computer. If it&#8217;s a general-purpose computer, then Apple will need to back down. They obviously can&#8217;t restrict applications in OS X, and probably shouldn&#8217;t be on the iPhone either.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
