<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title><![CDATA[Grist - Comment Feed for Do the emissions from a single Google search matter?]]></title>
	<atom:link href="http://www.grist.org/rss/" rel="self" type="application/rss+xml" />
	<description>Grist Comment Feed</description>
	<language>en</language>
    
		<item>
            <title>Comment #1 by Bart Anderson</title>
			<link>http://www.grist.org/article/Grams-be-damned/</link>
			<pubDate>Tue, 13 Jan 2009 03:27:45 -0800</pubDate>
			<guid isPermaLink="false">http://www.grist.org/article/Grams-be-damned/1</guid>
			<description><![CDATA[
				<p><strong>No shame, no guilt. Instead: insight<p><a href="http://www.timesonline.co.uk/tol/news/environment/article5488934.ece" rel="nofollow">From an interview with Dr Alex Wissner-Gross (UK Times) For a typical website experience, the dominant contribution to its footprint comes from the electricity consumed by its visitors' computers, followed by the network infrastructure needed to transmit the website, with the servers and data centers providing the website as the smallest contributor. <p>
Many prominent sites are, however, increasing emissions through software errors and other problems, which increase the time - and energy - needed to access them.  The emphasis on Google in the articles seems to be rather misleading. Google isn't really the issue - it's the entire structure of the web, including personal computers, networks, as well as the server farms.<p>
Since electricity for PCs is the dominant factor, the most effective response would be energy-efficient PCs and turning them off when not in use. Turning to green sources of electricity would reduce the carbon footprint.<p>
Dr. Wissner-Gross's point about the inefficiency of much web software is a good one. It's all too easy to design a website to be an energy hog. That's one of the reasons I've argued against needless complexity in website design. Simple interfaces also reduce the time you spend waiting for an article to display. 

<p>Bart<br>
<a href="http://energybulletin.net" rel="nofollow">Energy Bulletin</a></br></p></p></p></p></a></p></strong></p>
			]]></description>
			<content:encoded><![CDATA[
				<p><strong>No shame, no guilt. Instead: insight<p><a href="http://www.timesonline.co.uk/tol/news/environment/article5488934.ece" rel="nofollow">From an interview with Dr Alex Wissner-Gross (UK Times) For a typical website experience, the dominant contribution to its footprint comes from the electricity consumed by its visitors' computers, followed by the network infrastructure needed to transmit the website, with the servers and data centers providing the website as the smallest contributor. <p>
Many prominent sites are, however, increasing emissions through software errors and other problems, which increase the time - and energy - needed to access them.  The emphasis on Google in the articles seems to be rather misleading. Google isn't really the issue - it's the entire structure of the web, including personal computers, networks, as well as the server farms.<p>
Since electricity for PCs is the dominant factor, the most effective response would be energy-efficient PCs and turning them off when not in use. Turning to green sources of electricity would reduce the carbon footprint.<p>
Dr. Wissner-Gross's point about the inefficiency of much web software is a good one. It's all too easy to design a website to be an energy hog. That's one of the reasons I've argued against needless complexity in website design. Simple interfaces also reduce the time you spend waiting for an article to display. 

<p>Bart<br>
<a href="http://energybulletin.net" rel="nofollow">Energy Bulletin</a></br></p></p></p></p></a></p></strong></p>
			]]></content:encoded>
		</item>
    
 </channel>
</rss>