<?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: How the NYT Stumbled on the Google Nexus One Review</title>
	<atom:link href="http://i8-d.com/2010/01/05/how-the-nyt-stumbled-on-the-google-nexus-one-review/feed/" rel="self" type="application/rss+xml" />
	<link>http://i8-d.com/2010/01/05/how-the-nyt-stumbled-on-the-google-nexus-one-review/</link>
	<description>And you should eat him too!</description>
	<lastBuildDate>Tue, 30 Mar 2010 16:29:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: DeWayne Lehman</title>
		<link>http://i8-d.com/2010/01/05/how-the-nyt-stumbled-on-the-google-nexus-one-review/comment-page-1/#comment-36</link>
		<dc:creator>DeWayne Lehman</dc:creator>
		<pubDate>Wed, 06 Jan 2010 17:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://i8-d.com/?p=73#comment-36</guid>
		<description>If you mean the screen reader: http://blog.blindaccessjournal.com/2009/06/apple-announces-iphone-accessibility.html that is not the godsend.  It still leaves a gap in input, unless you wanna keep sliding over the onscreen keyboard hunting and pecking as it reads out the characters.  Voice input is the godsend, but a screen reader is the necessary second component to make it a complete package for the blind.  So no, Apple&#039;s solution is not &quot;complete&quot; as you called it.  I stick by my statement 100%.</description>
		<content:encoded><![CDATA[<p>If you mean the screen reader: <a href="http://blog.blindaccessjournal.com/2009/06/apple-announces-iphone-accessibility.html" rel="nofollow">http://blog.blindaccessjournal.com/2009/06/apple-announces-iphone-accessibility.html</a> that is not the godsend.  It still leaves a gap in input, unless you wanna keep sliding over the onscreen keyboard hunting and pecking as it reads out the characters.  Voice input is the godsend, but a screen reader is the necessary second component to make it a complete package for the blind.  So no, Apple&#8217;s solution is not &#8220;complete&#8221; as you called it.  I stick by my statement 100%.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Ryan</title>
		<link>http://i8-d.com/2010/01/05/how-the-nyt-stumbled-on-the-google-nexus-one-review/comment-page-1/#comment-35</link>
		<dc:creator>Michael Ryan</dc:creator>
		<pubDate>Wed, 06 Jan 2010 14:56:47 +0000</pubDate>
		<guid isPermaLink="false">http://i8-d.com/?p=73#comment-35</guid>
		<description>&quot;For the blind, this phone is a godsend! Voice input, and hopefully voice reading soon for all apps. What an incredible door that opens for the disabled that makes it their #1 choice.&quot;

You&#039;re totally kidding, right? 
the iPhone is the first and only phone to have COMPLETE touch-to-speech capability for the blind... you can control and &quot;feel&quot; EVERYTHING on the screen...have it read the buttons, zoom in to 800%, reverse the whites/blacks, the &quot;rotor&quot; to control preferences by touch... you can even operate the phone completely with the screen TOTALLY OFF... unbelievably complete and powerful for the blind. Check it out.

Compared with that, the Google phone would definitely not be a blind person&#039;s #1 choice!</description>
		<content:encoded><![CDATA[<p>&#8220;For the blind, this phone is a godsend! Voice input, and hopefully voice reading soon for all apps. What an incredible door that opens for the disabled that makes it their #1 choice.&#8221;</p>
<p>You&#8217;re totally kidding, right?<br />
the iPhone is the first and only phone to have COMPLETE touch-to-speech capability for the blind&#8230; you can control and &#8220;feel&#8221; EVERYTHING on the screen&#8230;have it read the buttons, zoom in to 800%, reverse the whites/blacks, the &#8220;rotor&#8221; to control preferences by touch&#8230; you can even operate the phone completely with the screen TOTALLY OFF&#8230; unbelievably complete and powerful for the blind. Check it out.</p>
<p>Compared with that, the Google phone would definitely not be a blind person&#8217;s #1 choice!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DeWayne Lehman</title>
		<link>http://i8-d.com/2010/01/05/how-the-nyt-stumbled-on-the-google-nexus-one-review/comment-page-1/#comment-34</link>
		<dc:creator>DeWayne Lehman</dc:creator>
		<pubDate>Wed, 06 Jan 2010 04:15:15 +0000</pubDate>
		<guid isPermaLink="false">http://i8-d.com/?p=73#comment-34</guid>
		<description>&quot; I’m not sure what some of your points are (I say Google’s voice-recognition is much better than the iPhone’s&quot;

You went on to say that the iPhone has an app that does the &quot;same thing&quot;.  If you mean change voice input to text output, that&#039;s a real over generalization. Mapquest in a browser and Google Maps on a mobile phone do the &quot;same thing&quot; basically, but they are radically different in use.  In functionality, Android does not do the same thing because of the integrated functionality, but you sounded a lot like the &quot;there&#039;s an app for that&quot; Apple commercial.  Only in this case, it was an app that doesn&#039;t even come close to the same functionality.  

&quot;I doubt very much that you’ve actually compared the two phones’ cameras, as I have&quot;

You didn&#039;t mention under what conditions those pictures were taken, which is what I asked.

&quot;megapixels means NOTHING to “photo quality”–only determines how many dots make up the one lousy picture!&quot;

Which I mentioned as well, that all things being equal, more is better, key part &quot;all things being equal&quot;.

As for the audience, I suspect a fully voice capable phone appeals to every audience still turned off from smartphones who don&#039;t, or can&#039;t, type on smart phones.  For instance, my elderly father and the blind.

For the blind, this phone is a godsend!  Voice input, and hopefully voice reading soon for all apps.  What an incredible door that opens for the disabled that makes it their #1 choice.

As for the iPhone polish, a null SMS message could crash them when it was released.  I wouldn&#039;t call that polished.  Not blaming them, bugs are bugs are bugs. iPhone had plenty of them, Nexus One will have their own share.

The actual point was simply that just about everything that is right with iPhone, they can do.  And most of things iPhone is lacking they do right.  Much of that has to do with the Android platform more than the HTC hardware.  But the distance between iPhone and Android is widening.  Most of the critiques you had lacked a specificity, and generalized and used vague references.

If you are going to review the camera, give a specific.  Put up side by side pictures at the minimum.  If you are going to talk about the crashes, tell me more than your background crashed.  Did you try other programs, were there other crashes, was this a phone problem or just a badly written background gadget.

I read a lot of opinion, not a lot of facts, nothing of factual comparison.  Everyone has an opinion, no doubt.  But many readers what some meat and potatoes in their reviews.

As for the layman audience, I am the Lehman, hehe, quite litterally.  I am not an Engadget or Gizmodo gadget specs freak.  I like phones, I like tech, and I work a blue collar job.  No blue collar worker I&#039;ve ever worked with subscribed to the NYT.  It&#039;s not quite &quot;general audience&quot; around here, it&#039;s considered high brow to many of them.

Much of the review felt like an iPhone lover writing a review that pained them to admit something might be better.

Many of the people I work with have Blackberries and iPhones.  No Palm Pre&#039;s that I&#039;ve seen.  When I talk to them about the features, users are looking to only two phones Droid and iPhone.  When I read some stories to them from my Blackberry about the Nexus, most responded the same way.  &quot;Wow, I bet that phone will cost a fortune!&quot;

I suppose us simple folk are fascinated by shiny gadgets, search by picture, and voice recognition.  But, that&#039;s what sells phones.  Usually a single feature or two.  Not lack of ringer buttons.

Don&#039;t get me wrong, I enjoyed the parts of your article that did the tit for tat comparisons.  I just found much of that lacking, with more opinion than anything.  I just didn&#039;t find much in the way of Tech, or even &quot;Tech for dummies&quot; as in how I compared the two displays.  It was some tech fact, some dumbed down explanation, and my opinion mixed in.

But hey, that&#039;s just my $0.02.  I&#039;m just an occasional blogger without a college degree in journalism, and that&#039;s why you are paid the big bucks for good reason.  Time will tell if this phone sells or flops.</description>
		<content:encoded><![CDATA[<p>&#8221; I’m not sure what some of your points are (I say Google’s voice-recognition is much better than the iPhone’s&#8221;</p>
<p>You went on to say that the iPhone has an app that does the &#8220;same thing&#8221;.  If you mean change voice input to text output, that&#8217;s a real over generalization. Mapquest in a browser and Google Maps on a mobile phone do the &#8220;same thing&#8221; basically, but they are radically different in use.  In functionality, Android does not do the same thing because of the integrated functionality, but you sounded a lot like the &#8220;there&#8217;s an app for that&#8221; Apple commercial.  Only in this case, it was an app that doesn&#8217;t even come close to the same functionality.  </p>
<p>&#8220;I doubt very much that you’ve actually compared the two phones’ cameras, as I have&#8221;</p>
<p>You didn&#8217;t mention under what conditions those pictures were taken, which is what I asked.</p>
<p>&#8220;megapixels means NOTHING to “photo quality”–only determines how many dots make up the one lousy picture!&#8221;</p>
<p>Which I mentioned as well, that all things being equal, more is better, key part &#8220;all things being equal&#8221;.</p>
<p>As for the audience, I suspect a fully voice capable phone appeals to every audience still turned off from smartphones who don&#8217;t, or can&#8217;t, type on smart phones.  For instance, my elderly father and the blind.</p>
<p>For the blind, this phone is a godsend!  Voice input, and hopefully voice reading soon for all apps.  What an incredible door that opens for the disabled that makes it their #1 choice.</p>
<p>As for the iPhone polish, a null SMS message could crash them when it was released.  I wouldn&#8217;t call that polished.  Not blaming them, bugs are bugs are bugs. iPhone had plenty of them, Nexus One will have their own share.</p>
<p>The actual point was simply that just about everything that is right with iPhone, they can do.  And most of things iPhone is lacking they do right.  Much of that has to do with the Android platform more than the HTC hardware.  But the distance between iPhone and Android is widening.  Most of the critiques you had lacked a specificity, and generalized and used vague references.</p>
<p>If you are going to review the camera, give a specific.  Put up side by side pictures at the minimum.  If you are going to talk about the crashes, tell me more than your background crashed.  Did you try other programs, were there other crashes, was this a phone problem or just a badly written background gadget.</p>
<p>I read a lot of opinion, not a lot of facts, nothing of factual comparison.  Everyone has an opinion, no doubt.  But many readers what some meat and potatoes in their reviews.</p>
<p>As for the layman audience, I am the Lehman, hehe, quite litterally.  I am not an Engadget or Gizmodo gadget specs freak.  I like phones, I like tech, and I work a blue collar job.  No blue collar worker I&#8217;ve ever worked with subscribed to the NYT.  It&#8217;s not quite &#8220;general audience&#8221; around here, it&#8217;s considered high brow to many of them.</p>
<p>Much of the review felt like an iPhone lover writing a review that pained them to admit something might be better.</p>
<p>Many of the people I work with have Blackberries and iPhones.  No Palm Pre&#8217;s that I&#8217;ve seen.  When I talk to them about the features, users are looking to only two phones Droid and iPhone.  When I read some stories to them from my Blackberry about the Nexus, most responded the same way.  &#8220;Wow, I bet that phone will cost a fortune!&#8221;</p>
<p>I suppose us simple folk are fascinated by shiny gadgets, search by picture, and voice recognition.  But, that&#8217;s what sells phones.  Usually a single feature or two.  Not lack of ringer buttons.</p>
<p>Don&#8217;t get me wrong, I enjoyed the parts of your article that did the tit for tat comparisons.  I just found much of that lacking, with more opinion than anything.  I just didn&#8217;t find much in the way of Tech, or even &#8220;Tech for dummies&#8221; as in how I compared the two displays.  It was some tech fact, some dumbed down explanation, and my opinion mixed in.</p>
<p>But hey, that&#8217;s just my $0.02.  I&#8217;m just an occasional blogger without a college degree in journalism, and that&#8217;s why you are paid the big bucks for good reason.  Time will tell if this phone sells or flops.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How the NYT Stumbled on the Google Nexus One Review &#124; Console Gaming</title>
		<link>http://i8-d.com/2010/01/05/how-the-nyt-stumbled-on-the-google-nexus-one-review/comment-page-1/#comment-33</link>
		<dc:creator>How the NYT Stumbled on the Google Nexus One Review &#124; Console Gaming</dc:creator>
		<pubDate>Wed, 06 Jan 2010 04:09:27 +0000</pubDate>
		<guid isPermaLink="false">http://i8-d.com/?p=73#comment-33</guid>
		<description>[...] post by I Ate DeWayne!  [...]</description>
		<content:encoded><![CDATA[<p>[...] post by I Ate DeWayne!  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Pogue</title>
		<link>http://i8-d.com/2010/01/05/how-the-nyt-stumbled-on-the-google-nexus-one-review/comment-page-1/#comment-32</link>
		<dc:creator>David Pogue</dc:creator>
		<pubDate>Wed, 06 Jan 2010 03:39:59 +0000</pubDate>
		<guid isPermaLink="false">http://i8-d.com/?p=73#comment-32</guid>
		<description>Interesting critique. I&#039;m not sure what some of your points are (I say Google&#039;s voice-recognition is much better than the iPhone&#039;s, because you can dictate into any text box; you say exactly the same thing)... and I doubt very much that you&#039;ve actually compared the two phones&#039; cameras, as I have. (An LED flash is nice, but only in certain situations; and megapixels means NOTHING to &quot;photo quality&quot;--only determines how many dots make up the one lousy picture!)

As for my being &quot;out of touch with who the real audience the Google Nexus One is for&quot;... I wouldn&#039;t put it that way. I write for a layman audience. I&#039;d definitely expect Engadget or Gizmodo to LOVE the Nexus (although they didn&#039;t), because the Nexus is a pretty geeky phone, and it&#039;s targeted at geeks. Definitely more complex than, say, iPhone. And not nearly as polished--come on, error messages and freezes on your PHONE? That&#039;s not cool.

But to your point: You&#039;re right. The Times is for a general audience. I might have written a different review if I were writing for gadget freaks.

--Pogue</description>
		<content:encoded><![CDATA[<p>Interesting critique. I&#8217;m not sure what some of your points are (I say Google&#8217;s voice-recognition is much better than the iPhone&#8217;s, because you can dictate into any text box; you say exactly the same thing)&#8230; and I doubt very much that you&#8217;ve actually compared the two phones&#8217; cameras, as I have. (An LED flash is nice, but only in certain situations; and megapixels means NOTHING to &#8220;photo quality&#8221;&#8211;only determines how many dots make up the one lousy picture!)</p>
<p>As for my being &#8220;out of touch with who the real audience the Google Nexus One is for&#8221;&#8230; I wouldn&#8217;t put it that way. I write for a layman audience. I&#8217;d definitely expect Engadget or Gizmodo to LOVE the Nexus (although they didn&#8217;t), because the Nexus is a pretty geeky phone, and it&#8217;s targeted at geeks. Definitely more complex than, say, iPhone. And not nearly as polished&#8211;come on, error messages and freezes on your PHONE? That&#8217;s not cool.</p>
<p>But to your point: You&#8217;re right. The Times is for a general audience. I might have written a different review if I were writing for gadget freaks.</p>
<p>&#8211;Pogue</p>
]]></content:encoded>
	</item>
</channel>
</rss>
