<?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: Star Trek Fun: Replicator versus Holodeck</title>
	<atom:link href="http://radoff.com/blog/2009/05/10/star-trek-fun-replicator-versus-holodeck/feed/" rel="self" type="application/rss+xml" />
	<link>http://radoff.com/blog/2009/05/10/star-trek-fun-replicator-versus-holodeck/</link>
	<description>Swashbuckler, adventurer, slayer of dragons, commando, storyteller, Internet entrepreneur; explorer of rabbit holes</description>
	<lastBuildDate>Wed, 25 Aug 2010 19:48:26 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Hagan</title>
		<link>http://radoff.com/blog/2009/05/10/star-trek-fun-replicator-versus-holodeck/comment-page-1/#comment-3909</link>
		<dc:creator>Hagan</dc:creator>
		<pubDate>Fri, 22 May 2009 22:47:58 +0000</pubDate>
		<guid isPermaLink="false">http://radoff.com/blog/?p=67#comment-3909</guid>
		<description>A few things that may (or may not) have come up about the Holodeck and Replicator&#039;s.

Replicators need a template to work off.  Now normally that would consist of having one of said products available and &#039;feeding&#039; it into the replicator first (so you&#039;d still need to buy stuff).  True, you could make hundreds from the template, but if the original unit was flawed, so would the copies.  Plus whatever you copy is limited in size to the replication port, so unless you go for the BIG ones (which need a building, security and one hell of a power source) your knackered for many business ventures.

Holodecks, good for training, games, simulations and so on.  But that comes with problems of its own, for a start, how do you program them?  A vast computer banks worth of imaging data of course.... which needs a 3D camera to capture the data.  For that, you&#039;ll need a tricorder set-up for capturing three dimensional sensor data.  The other options are too A) place objects within the holodeck to be scanned and recorded or B) Feed millions of pictures into the holodeck computer and hope it can extrapolate all the data without freezing up.

If it where me, I&#039;d go for the replicator.  Sure it gives out free stuff, but it also uses up a lot of power.  If the electric bill is reasonable, I&#039;d keep it.  Besides, how many times have you come across the perfect sandwich, packet of crisps (Chips) or cup of coffee and wanted to keep drinking/eating it long after it was done with...?  Well, now you can.

And, the replicator becomes a good repository for an increasing amount of stuff too.  Got 100&#039;s of books, cd&#039;s, dvd&#039;s and other stuff you don&#039;t want collecting dust, but still want access to them?  Just store them in your handy replicator and hey presto, you have more room.  When did you last see people having to hang a shelf on the Enterprise D?  That&#039;s because they didn&#039;t need them.

Just a few thoughts.</description>
		<content:encoded><![CDATA[<p>A few things that may (or may not) have come up about the Holodeck and Replicator&#8217;s.</p>
<p>Replicators need a template to work off.  Now normally that would consist of having one of said products available and &#8216;feeding&#8217; it into the replicator first (so you&#8217;d still need to buy stuff).  True, you could make hundreds from the template, but if the original unit was flawed, so would the copies.  Plus whatever you copy is limited in size to the replication port, so unless you go for the BIG ones (which need a building, security and one hell of a power source) your knackered for many business ventures.</p>
<p>Holodecks, good for training, games, simulations and so on.  But that comes with problems of its own, for a start, how do you program them?  A vast computer banks worth of imaging data of course&#8230;. which needs a 3D camera to capture the data.  For that, you&#8217;ll need a tricorder set-up for capturing three dimensional sensor data.  The other options are too A) place objects within the holodeck to be scanned and recorded or B) Feed millions of pictures into the holodeck computer and hope it can extrapolate all the data without freezing up.</p>
<p>If it where me, I&#8217;d go for the replicator.  Sure it gives out free stuff, but it also uses up a lot of power.  If the electric bill is reasonable, I&#8217;d keep it.  Besides, how many times have you come across the perfect sandwich, packet of crisps (Chips) or cup of coffee and wanted to keep drinking/eating it long after it was done with&#8230;?  Well, now you can.</p>
<p>And, the replicator becomes a good repository for an increasing amount of stuff too.  Got 100&#8217;s of books, cd&#8217;s, dvd&#8217;s and other stuff you don&#8217;t want collecting dust, but still want access to them?  Just store them in your handy replicator and hey presto, you have more room.  When did you last see people having to hang a shelf on the Enterprise D?  That&#8217;s because they didn&#8217;t need them.</p>
<p>Just a few thoughts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
