<?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: Strange Names for Strange Days</title>
	<atom:link href="http://www.linux-mag.com/id/4137/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.linux-mag.com/id/4137/</link>
	<description>Open Source, Open Standards</description>
	<lastBuildDate>Sat, 05 Oct 2013 13:48:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: yoof</title>
		<link>http://www.linux-mag.com/id/4137/#comment-4624</link>
		<dc:creator>yoof</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/4137/#comment-4624</guid>
		<description>There was a time when we designed in FORTRAN, but then coded the tricky bits (that needed to be efficient) in assembler macros. I wonder if now we should design with something like LISP (with OO and implicit parallelization) but code the tricky bits in C?</description>
		<content:encoded><![CDATA[<p>There was a time when we designed in FORTRAN, but then coded the tricky bits (that needed to be efficient) in assembler macros. I wonder if now we should design with something like LISP (with OO and implicit parallelization) but code the tricky bits in C?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nimityssj</title>
		<link>http://www.linux-mag.com/id/4137/#comment-4625</link>
		<dc:creator>nimityssj</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/4137/#comment-4625</guid>
		<description>I&#039;ve been pushing parallel languages for a while, and it&#039;s good to see a piece on it. I&#039;m surprised the author didn&#039;t mention MIT&#039;s Cilk, which adds like 3 statements to the C lang. and the runtime parallelizes from there. The Nesl language, from CMU, has been used on numerous clusters, and supposedly can reduce code size significantly: on their quicksort it was &quot;10 lines of code vs. 1700&quot;, compared to C++/MPI. Executed effeciently, too. I believe that if we are to deal with the complexity of parallel hardware, we will need better tools, like these, to do it.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been pushing parallel languages for a while, and it&#8217;s good to see a piece on it. I&#8217;m surprised the author didn&#8217;t mention MIT&#8217;s Cilk, which adds like 3 statements to the C lang. and the runtime parallelizes from there. The Nesl language, from CMU, has been used on numerous clusters, and supposedly can reduce code size significantly: on their quicksort it was &#8220;10 lines of code vs. 1700&#8243;, compared to C++/MPI. Executed effeciently, too. I believe that if we are to deal with the complexity of parallel hardware, we will need better tools, like these, to do it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nimityssj</title>
		<link>http://www.linux-mag.com/id/4137/#comment-4626</link>
		<dc:creator>nimityssj</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.linux-mag.com/id/4137/#comment-4626</guid>
		<description>TO YOOF:&lt;br /&gt;
&lt;br /&gt;
That was an excellent idea, and I have been asking the Erlang and Nesl people about this. I figure that if the critical, serial routines could be coded in C/C++ (i prefer C++), then incorporated into the parallel lang. code like how Java binds native code, then we could have the best of both worlds. Well, close enough.&lt;br /&gt;
&lt;br /&gt;
Is there anyone out there who develops with these languages or dev.&#039;s the lang.&#039;s themselves? Would like your input on this, but with Erlang (my favorite for HA systems), there are some limitations to this approach. Perhaps it will be addressed later. Might be better off just modifying a high-performance Common LISP system, like AllegroCL. HPC LISP (*LISP) was one of the first languages for this stuff, used on the Thinking Machines Corp.&#039;s 64,000 processor systems.</description>
		<content:encoded><![CDATA[<p>TO YOOF:</p>
<p>That was an excellent idea, and I have been asking the Erlang and Nesl people about this. I figure that if the critical, serial routines could be coded in C/C++ (i prefer C++), then incorporated into the parallel lang. code like how Java binds native code, then we could have the best of both worlds. Well, close enough.</p>
<p>Is there anyone out there who develops with these languages or dev.&#8217;s the lang.&#8217;s themselves? Would like your input on this, but with Erlang (my favorite for HA systems), there are some limitations to this approach. Perhaps it will be addressed later. Might be better off just modifying a high-performance Common LISP system, like AllegroCL. HPC LISP (*LISP) was one of the first languages for this stuff, used on the Thinking Machines Corp.&#8217;s 64,000 processor systems.</p>
]]></content:encoded>
	</item>
</channel>
</rss>