<?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: Next-Gen Nuclear Tech Could Face Delays in Wake of Japan Incident</title>
	<atom:link href="http://gigaom.com/2011/03/16/next-gen-nuclear-tech-development-could-come-to-a-screeching-halt/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2011/03/16/next-gen-nuclear-tech-development-could-come-to-a-screeching-halt/</link>
	<description></description>
	<lastBuildDate>Thu, 20 Jun 2013 07:25:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Gary Ambrosino</title>
		<link>http://gigaom.com/2011/03/16/next-gen-nuclear-tech-development-could-come-to-a-screeching-halt/#comment-610392</link>
		<dc:creator><![CDATA[Gary Ambrosino]]></dc:creator>
		<pubDate>Sun, 20 Mar 2011 23:57:04 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=318575#comment-610392</guid>
		<description><![CDATA[I think Ray is, unfortunately, right to some degree with his analysis.  The unfortunate outcome of the Japan nuclear incident is that it showcases the weaknesses of 40 year old reactor technology.   I look at that era of nuclear energy the same way we looked at early computer operating systems - - single threaded, non-redundant, fragile, and hard to operate.   People like NuScale are taking an approach more akin to our current redundant and distributed computing platforms that are pervasive now, but weren&#039;t back when people complained about using computers for anything mission critical like fly-by-wire flight controls systems.   Companies like Areva make recent generation plants much safer, especially with the post-processing of fuel where Areva builds spent fuel processing facilities that significantly reduce the half-life of the spent material, reprocess it so it cannot be used in any way to make weapons, and reduce the physical mass to make it easier and safer to transport.    Wouldn&#039;t it be great if there were as many blogs, websites, industry pundits &amp; gurus, and enthusiastic educators about these aspects of nuclear power, as there are blogs talking about the latest features if the iPad2.   Then we would have a better head start on shutting down the import addiction to oil.]]></description>
		<content:encoded><![CDATA[<p>I think Ray is, unfortunately, right to some degree with his analysis.  The unfortunate outcome of the Japan nuclear incident is that it showcases the weaknesses of 40 year old reactor technology.   I look at that era of nuclear energy the same way we looked at early computer operating systems &#8211; - single threaded, non-redundant, fragile, and hard to operate.   People like NuScale are taking an approach more akin to our current redundant and distributed computing platforms that are pervasive now, but weren&#8217;t back when people complained about using computers for anything mission critical like fly-by-wire flight controls systems.   Companies like Areva make recent generation plants much safer, especially with the post-processing of fuel where Areva builds spent fuel processing facilities that significantly reduce the half-life of the spent material, reprocess it so it cannot be used in any way to make weapons, and reduce the physical mass to make it easier and safer to transport.    Wouldn&#8217;t it be great if there were as many blogs, websites, industry pundits &amp; gurus, and enthusiastic educators about these aspects of nuclear power, as there are blogs talking about the latest features if the iPad2.   Then we would have a better head start on shutting down the import addiction to oil.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
