<?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: From C# on Mono, to Clojure on the JVM</title>
	<atom:link href="http://blog.agilehead.com/content/from-c-on-mono-to-clojure-on-the-jvm/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.agilehead.com/content/from-c-on-mono-to-clojure-on-the-jvm/</link>
	<description>About building great applications before christmas.</description>
	<lastBuildDate>Sat, 07 Nov 2009 04:42:09 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nick B</title>
		<link>http://blog.agilehead.com/content/from-c-on-mono-to-clojure-on-the-jvm/comment-page-1/#comment-25</link>
		<dc:creator>Nick B</dc:creator>
		<pubDate>Tue, 30 Jun 2009 03:59:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilehead.com/?p=10#comment-25</guid>
		<description>&gt; Also, you might consider looking at the “D” language for applications that will need to connect to native C/C++ libraries, e.g. desktop apps. Where Clojure feels like “Lisp done right”, D is “C++ done right”.

To be precise - check out &quot;D programming language&quot; &amp;  &quot;TANGO&quot;  (the framework).</description>
		<content:encoded><![CDATA[<p>&gt; Also, you might consider looking at the “D” language for applications that will need to connect to native C/C++ libraries, e.g. desktop apps. Where Clojure feels like “Lisp done right”, D is “C++ done right”.</p>
<p>To be precise &#8211; check out &#8220;D programming language&#8221; &amp;  &#8220;TANGO&#8221;  (the framework).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://blog.agilehead.com/content/from-c-on-mono-to-clojure-on-the-jvm/comment-page-1/#comment-22</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 23 Jun 2009 08:55:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilehead.com/?p=10#comment-22</guid>
		<description>And what about F# ?</description>
		<content:encoded><![CDATA[<p>And what about F# ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://blog.agilehead.com/content/from-c-on-mono-to-clojure-on-the-jvm/comment-page-1/#comment-21</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Tue, 23 Jun 2009 06:13:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilehead.com/?p=10#comment-21</guid>
		<description>Lisp will not win!
(Too (many) pa(r) ent (hese) s)

There has to be a reason why Lisp didn&#039;t pick up since when it was introduced.... readability. 

Parens indicate in literature (a side thought) or something that can be skipped. 

It is just not natural to express 2+2 as (+(2,2)) or whatever, in code. 

IMHO, it will forever remain a cult language. Something like Sanskrit, Latin etc - good to know and helpful to understand the finer things in (coding (can&#039;t resist)) life!</description>
		<content:encoded><![CDATA[<p>Lisp will not win!<br />
(Too (many) pa(r) ent (hese) s)</p>
<p>There has to be a reason why Lisp didn&#8217;t pick up since when it was introduced&#8230;. readability. </p>
<p>Parens indicate in literature (a side thought) or something that can be skipped. </p>
<p>It is just not natural to express 2+2 as (+(2,2)) or whatever, in code. </p>
<p>IMHO, it will forever remain a cult language. Something like Sanskrit, Latin etc &#8211; good to know and helpful to understand the finer things in (coding (can&#8217;t resist)) life!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amr</title>
		<link>http://blog.agilehead.com/content/from-c-on-mono-to-clojure-on-the-jvm/comment-page-1/#comment-16</link>
		<dc:creator>Amr</dc:creator>
		<pubDate>Mon, 15 Jun 2009 12:18:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilehead.com/?p=10#comment-16</guid>
		<description>you can still stick with Mono though. &lt;a href=&#039;http://boo.codehaus.org/&#039; rel=&quot;nofollow&quot;&gt;Boo&lt;/a&gt; and &lt;a href=&#039;http://nemerle.org/Main_Page&#039; rel=&quot;nofollow&quot;&gt;Nemrle&lt;/a&gt; deserves your attention !</description>
		<content:encoded><![CDATA[<p>you can still stick with Mono though. <a href='http://boo.codehaus.org/' rel="nofollow">Boo</a> and <a href='http://nemerle.org/Main_Page' rel="nofollow">Nemrle</a> deserves your attention !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://blog.agilehead.com/content/from-c-on-mono-to-clojure-on-the-jvm/comment-page-1/#comment-15</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Mon, 15 Jun 2009 05:35:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilehead.com/?p=10#comment-15</guid>
		<description>Strictly speaking, both Fortran and Lisp are older then Cobol...</description>
		<content:encoded><![CDATA[<p>Strictly speaking, both Fortran and Lisp are older then Cobol&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark</title>
		<link>http://blog.agilehead.com/content/from-c-on-mono-to-clojure-on-the-jvm/comment-page-1/#comment-13</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Sun, 14 Jun 2009 14:09:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilehead.com/?p=10#comment-13</guid>
		<description>Cobol will be the 100 year language first, it&#039;s already 50....

:D</description>
		<content:encoded><![CDATA[<p>Cobol will be the 100 year language first, it&#8217;s already 50&#8230;.</p>
<p>:D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacques Chester</title>
		<link>http://blog.agilehead.com/content/from-c-on-mono-to-clojure-on-the-jvm/comment-page-1/#comment-12</link>
		<dc:creator>Jacques Chester</dc:creator>
		<pubDate>Sun, 14 Jun 2009 06:10:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilehead.com/?p=10#comment-12</guid>
		<description>Nitpick:

It&#039;s generally referred to as &quot;Lisp&quot;, not &quot;LISP&quot;.</description>
		<content:encoded><![CDATA[<p>Nitpick:</p>
<p>It&#8217;s generally referred to as &#8220;Lisp&#8221;, not &#8220;LISP&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeswinpk</title>
		<link>http://blog.agilehead.com/content/from-c-on-mono-to-clojure-on-the-jvm/comment-page-1/#comment-11</link>
		<dc:creator>jeswinpk</dc:creator>
		<pubDate>Sun, 14 Jun 2009 03:17:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilehead.com/?p=10#comment-11</guid>
		<description>@Steve 

Just like most other failures, ours had little to do with our choice of technology. I was suggesting that the choice of technology is a small company (or a small group of programmers), serves to drum up interest and enthusiasm. 

As long as the interface remains the same and the app is fast, I don&#039;t think users will care. And as I was saying, those Mono services never needed restarts - so Mono really served us well as far as the technology is concerned.</description>
		<content:encoded><![CDATA[<p>@Steve </p>
<p>Just like most other failures, ours had little to do with our choice of technology. I was suggesting that the choice of technology is a small company (or a small group of programmers), serves to drum up interest and enthusiasm. </p>
<p>As long as the interface remains the same and the app is fast, I don&#8217;t think users will care. And as I was saying, those Mono services never needed restarts &#8211; so Mono really served us well as far as the technology is concerned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Kos</title>
		<link>http://blog.agilehead.com/content/from-c-on-mono-to-clojure-on-the-jvm/comment-page-1/#comment-10</link>
		<dc:creator>Steve Kos</dc:creator>
		<pubDate>Sun, 14 Jun 2009 02:40:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilehead.com/?p=10#comment-10</guid>
		<description>I&#039;m puzzled.

A few years ago, you took a risky bet and decided to base your company on an obscure and potentially dangerous technology.

That project failed for exactly the reasons you suspected when you made that decision.

And now you want to make the same mistake by basing your company on yet another bleeding edge technology?

If seems to me you are more interested in experimenting with fun software stuff than building a sound business.

As for the hundred year language, I&#039;m betting that C# or Java is probably in a better position to achieve that goal than any of the other languages you listed in this post.

Good luck, though, I admire your bravado :-)</description>
		<content:encoded><![CDATA[<p>I&#8217;m puzzled.</p>
<p>A few years ago, you took a risky bet and decided to base your company on an obscure and potentially dangerous technology.</p>
<p>That project failed for exactly the reasons you suspected when you made that decision.</p>
<p>And now you want to make the same mistake by basing your company on yet another bleeding edge technology?</p>
<p>If seems to me you are more interested in experimenting with fun software stuff than building a sound business.</p>
<p>As for the hundred year language, I&#8217;m betting that C# or Java is probably in a better position to achieve that goal than any of the other languages you listed in this post.</p>
<p>Good luck, though, I admire your bravado :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jjames</title>
		<link>http://blog.agilehead.com/content/from-c-on-mono-to-clojure-on-the-jvm/comment-page-1/#comment-9</link>
		<dc:creator>jjames</dc:creator>
		<pubDate>Sun, 14 Jun 2009 01:38:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agilehead.com/?p=10#comment-9</guid>
		<description>Lots of smart hackers are already using Clojure.</description>
		<content:encoded><![CDATA[<p>Lots of smart hackers are already using Clojure.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
