<?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: Re: Redesigning GHC’s build system</title>
	<atom:link href="http://therning.org/magnus/archives/417/feed" rel="self" type="application/rss+xml" />
	<link>http://therning.org/magnus/archives/417</link>
	<description>Incoherent mumblings</description>
	<lastBuildDate>Sat, 23 Jan 2010 20:40:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: nominolo</title>
		<link>http://therning.org/magnus/archives/417/comment-page-1#comment-163230</link>
		<dc:creator>nominolo</dc:creator>
		<pubDate>Thu, 27 Nov 2008 23:42:47 +0000</pubDate>
		<guid isPermaLink="false">http://therning.org/magnus/?p=417#comment-163230</guid>
		<description>&lt;p&gt;FWIW, &lt;code&gt;make&lt;/code&gt; it is hard to beat in mindshare, ease of installation and, related, build dependencies.  Ian and SimonM know &lt;code&gt;make&lt;/code&gt;, and one big reason was to also make the build-system more accessible to new developers (ATM, a lot of the logic is implemented in Cabal itself or even indirectly through code generated by Cabal).  Switching to a completely new system would therefore be a loss for all participants; so it was pretty much a no-brainer.  Sure, &lt;code&gt;make&lt;/code&gt; has its weaknesses, but so have all the other tools out there.  At one point, GHC may be able to completely use Cabal and it&#039;s current in-development make-framework, but we cannot expect this to become better than &lt;code&gt;make&lt;/code&gt; anytime soon.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>FWIW, <code>make</code> it is hard to beat in mindshare, ease of installation and, related, build dependencies.  Ian and SimonM know <code>make</code>, and one big reason was to also make the build-system more accessible to new developers (ATM, a lot of the logic is implemented in Cabal itself or even indirectly through code generated by Cabal).  Switching to a completely new system would therefore be a loss for all participants; so it was pretty much a no-brainer.  Sure, <code>make</code> has its weaknesses, but so have all the other tools out there.  At one point, GHC may be able to completely use Cabal and it&#8217;s current in-development make-framework, but we cannot expect this to become better than <code>make</code> anytime soon.</p>]]></content:encoded>
	</item>
</channel>
</rss>
