<?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: How to save $149,850 per nanotechnology experiment</title>
	<atom:link href="http://www.foresight.org/nanodot/?feed=rss2&#038;p=2341" rel="self" type="application/rss+xml" />
	<link>http://www.foresight.org/nanodot/?p=2341</link>
	<description>examining transformative technology</description>
	<lastBuildDate>Wed, 03 Apr 2013 18:23:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: NanoEnthusiast</title>
		<link>http://www.foresight.org/nanodot/?p=2341#comment-49790</link>
		<dc:creator>NanoEnthusiast</dc:creator>
		<pubDate>Tue, 17 Oct 2006 04:13:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=2341#comment-49790</guid>
		<description>Perhaps we need at least the option to export in a universal format, but still have formats unique to each software package. Most word processors and 3d animation packages have data formats that are used only by the vendor, and yet you can still export to something neutral and continue where you left-off in another package. At any rate, NanoEngineer-1 is supposed to be released as open source, so there will be plenty of documentation regarding their file format(s) in the source code. Licensing issues permitting, there will be ways for other software to import and export NanoEngineer-1 files either natively or through plug-ins.</description>
		<content:encoded><![CDATA[<p>Perhaps we need at least the option to export in a universal format, but still have formats unique to each software package. Most word processors and 3d animation packages have data formats that are used only by the vendor, and yet you can still export to something neutral and continue where you left-off in another package. At any rate, NanoEngineer-1 is supposed to be released as open source, so there will be plenty of documentation regarding their file format(s) in the source code. Licensing issues permitting, there will be ways for other software to import and export NanoEngineer-1 files either natively or through plug-ins.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlos Bray</title>
		<link>http://www.foresight.org/nanodot/?p=2341#comment-49784</link>
		<dc:creator>Carlos Bray</dc:creator>
		<pubDate>Tue, 17 Oct 2006 02:28:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=2341#comment-49784</guid>
		<description>I think it&#039;s a moot  point because once there was a need for translation from one format to another some guy will make a program for just that very thing. The exact same way there are programs that allow you to change the format of a image file.</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s a moot  point because once there was a need for translation from one format to another some guy will make a program for just that very thing. The exact same way there are programs that allow you to change the format of a image file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Novak</title>
		<link>http://www.foresight.org/nanodot/?p=2341#comment-49455</link>
		<dc:creator>John Novak</dc:creator>
		<pubDate>Sat, 14 Oct 2006 16:41:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=2341#comment-49455</guid>
		<description>&lt;i&gt;I hope that there is, or will emerge, a standard file format for this kind of work. It does no one any good to have a tower of Babel situation where different research communities can’t use each others files.&lt;/i&gt;

I respectfully disagree.

At this stage of the game, the best format for nanotech simulations is not known.  The virtue in the babel situation is this: by not agreeing to a particular set of files and formats and methodologies, the babel promotes experimentation and exploration of the design space, making it more likely that over time, even better approaches than the ones we have now will be discovered.  Early centralization and pre-mature convergence are bad things, not good things. 

Moreover, I find it exceedingly unlikely that there will be found a universally &quot;best format&quot; for these sorts of things, any more than there is a universally &quot;best programming language&quot; even after decades of research into computer science.  The lesson taken from computer science, rather, is that different goals are enabled by different techniques.

We don&#039;t want total anarchy, no, but we don&#039;t want total conformity, either.</description>
		<content:encoded><![CDATA[<p><i>I hope that there is, or will emerge, a standard file format for this kind of work. It does no one any good to have a tower of Babel situation where different research communities can’t use each others files.</i></p>
<p>I respectfully disagree.</p>
<p>At this stage of the game, the best format for nanotech simulations is not known.  The virtue in the babel situation is this: by not agreeing to a particular set of files and formats and methodologies, the babel promotes experimentation and exploration of the design space, making it more likely that over time, even better approaches than the ones we have now will be discovered.  Early centralization and pre-mature convergence are bad things, not good things. </p>
<p>Moreover, I find it exceedingly unlikely that there will be found a universally &#8220;best format&#8221; for these sorts of things, any more than there is a universally &#8220;best programming language&#8221; even after decades of research into computer science.  The lesson taken from computer science, rather, is that different goals are enabled by different techniques.</p>
<p>We don&#8217;t want total anarchy, no, but we don&#8217;t want total conformity, either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NanoEnthusiast</title>
		<link>http://www.foresight.org/nanodot/?p=2341#comment-49020</link>
		<dc:creator>NanoEnthusiast</dc:creator>
		<pubDate>Fri, 13 Oct 2006 00:19:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=2341#comment-49020</guid>
		<description>It is my understanding that the Nanorex software has specific tools relevant to MNT work, i.e. tools to help define MNT parts (like bearings) parametrically that can then be optimized at a later stage to reduce chemical instabilities. From what little I can tell, this package would not have any of that. This package however, has tools relevant to general crystalline growth and nanotube creation as basic primitives. 

I hope that there is, or will emerge, a standard file format for this kind of work. It does no one any good to have a tower of Babel situation where different research communities can&#039;t use each others files. Also it is important (in order to head off any skepticism) to make sure that any interesting discoveries made in NanoEngineer-1 can be easily duplicated in other software applications.</description>
		<content:encoded><![CDATA[<p>It is my understanding that the Nanorex software has specific tools relevant to MNT work, i.e. tools to help define MNT parts (like bearings) parametrically that can then be optimized at a later stage to reduce chemical instabilities. From what little I can tell, this package would not have any of that. This package however, has tools relevant to general crystalline growth and nanotube creation as basic primitives. </p>
<p>I hope that there is, or will emerge, a standard file format for this kind of work. It does no one any good to have a tower of Babel situation where different research communities can&#8217;t use each others files. Also it is important (in order to head off any skepticism) to make sure that any interesting discoveries made in NanoEngineer-1 can be easily duplicated in other software applications.</p>
]]></content:encoded>
	</item>
</channel>
</rss>