<?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: Nook eReader &#8211; why the dual screen UI is slow</title>
	<atom:link href="http://ireaderreview.com/2009/12/05/nook-ereader-dual-screen-ui-slow/feed/" rel="self" type="application/rss+xml" />
	<link>http://ireaderreview.com/2009/12/05/nook-ereader-dual-screen-ui-slow/</link>
	<description>Kindle Review, Kindle Fire Review, New Kindle Review, Kindle 4 Review</description>
	<lastBuildDate>Sat, 26 May 2012 22:36:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Odds, Ends, and meet my Kindle.</title>
		<link>http://ireaderreview.com/2009/12/05/nook-ereader-dual-screen-ui-slow/#comment-7907</link>
		<dc:creator><![CDATA[Odds, Ends, and meet my Kindle.]]></dc:creator>
		<pubDate>Sun, 06 Dec 2009 19:43:16 +0000</pubDate>
		<guid isPermaLink="false">http://ireaderreview.com/?p=8369#comment-7907</guid>
		<description><![CDATA[[...] Some Kindle News:  First &#8211; there was a post on Engadget.com yesterday with some photos and reviews of the Nook yesterday. The link was originally here: http://www.engadget.com/2009/12/04/barnes-and-nobles-nook-gets-a-brief-and-early-hands-on/ but it looks like its been taken down. First impressions were that the browser/operating system was sluggish. IReader Review goes into further detail here. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Some Kindle News:  First &#8211; there was a post on Engadget.com yesterday with some photos and reviews of the Nook yesterday. The link was originally here: <a href="http://www.engadget.com/2009/12/04/barnes-and-nobles-nook-gets-a-brief-and-early-hands-on/" rel="nofollow">http://www.engadget.com/2009/12/04/barnes-and-nobles-nook-gets-a-brief-and-early-hands-on/</a> but it looks like its been taken down. First impressions were that the browser/operating system was sluggish. IReader Review goes into further detail here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nook Review on Twitter (BN staff), Nook starts shipping &#171; Kindle Review &#8211; Kindle 2 Review, Books</title>
		<link>http://ireaderreview.com/2009/12/05/nook-ereader-dual-screen-ui-slow/#comment-7881</link>
		<dc:creator><![CDATA[Nook Review on Twitter (BN staff), Nook starts shipping &#171; Kindle Review &#8211; Kindle 2 Review, Books]]></dc:creator>
		<pubDate>Sun, 06 Dec 2009 09:43:06 +0000</pubDate>
		<guid isPermaLink="false">http://ireaderreview.com/?p=8369#comment-7881</guid>
		<description><![CDATA[[...] 6, 2009 by switch11   The second Nook review (if you can call 3 twitter tweets that) matches the first. If the first 2 nook mini reviews are true the Kindle will see a sales boost now.   Now two [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 6, 2009 by switch11   The second Nook review (if you can call 3 twitter tweets that) matches the first. If the first 2 nook mini reviews are true the Kindle will see a sales boost now.   Now two [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://ireaderreview.com/2009/12/05/nook-ereader-dual-screen-ui-slow/#comment-7864</link>
		<dc:creator><![CDATA[david]]></dc:creator>
		<pubDate>Sun, 06 Dec 2009 00:04:43 +0000</pubDate>
		<guid isPermaLink="false">http://ireaderreview.com/?p=8369#comment-7864</guid>
		<description><![CDATA[Yeah that kinda seems true. Makes sense if you think about it.. it will make you notice the slow refresh. Good post.]]></description>
		<content:encoded><![CDATA[<p>Yeah that kinda seems true. Makes sense if you think about it.. it will make you notice the slow refresh. Good post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

