<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Kindle: Amazon’s electronic book reader</title>
	<link>http://www.carboncommentary.com/2007/11/26/60</link>
	<description>A critical appraisal of issues in the move to a low-carbon economy</description>
	<pubDate>Sat, 05 Jul 2008 01:18:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Duncan Clark</title>
		<link>http://www.carboncommentary.com/2007/11/26/60#comment-481</link>
		<dc:creator>Duncan Clark</dc:creator>
		<pubDate>Fri, 18 Apr 2008 12:02:42 +0000</pubDate>
		<guid>http://www.carboncommentary.com/2007/11/26/60#comment-481</guid>
		<description>Interesting, but two points:

1) Most people you identify as potential e-reader users already carry around a laptop and a phone. Why would the lawyer email a document to an e-reader instead of just reading it on the laptop (especially as these get smaller and lighter) or the phone (already possible on many models)? Do people really want to buy, carry, maintain and charge *three* devices simply to get three different screen sizes?

2) How can we estimate the carbon savings without identifying the carbon emissions of manufacturing a few tens of millions of e-readers?</description>
		<content:encoded><![CDATA[<p>Interesting, but two points:</p>
<p>1) Most people you identify as potential e-reader users already carry around a laptop and a phone. Why would the lawyer email a document to an e-reader instead of just reading it on the laptop (especially as these get smaller and lighter) or the phone (already possible on many models)? Do people really want to buy, carry, maintain and charge *three* devices simply to get three different screen sizes?</p>
<p>2) How can we estimate the carbon savings without identifying the carbon emissions of manufacturing a few tens of millions of e-readers?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
