<?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: Rails and Django</title>
	<atom:link href="http://blog.jeffhui.net/2009/03/rails-and-django/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jeffhui.net/2009/03/rails-and-django/</link>
	<description>A blog about programming and random other things.</description>
	<lastBuildDate>Wed, 14 Jul 2010 02:07:03 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: air jordan shoes</title>
		<link>http://blog.jeffhui.net/2009/03/rails-and-django/comment-page-1/#comment-143</link>
		<dc:creator>air jordan shoes</dc:creator>
		<pubDate>Mon, 05 Jul 2010 09:50:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jeffhui.net/2009/03/rails-and-django/#comment-143</guid>
		<description>Mark S. is definitely on the right track. If you want to get a professional looking email address, Id recommend buying your name domain name, like or  &lt;br&gt;&lt;a href=&quot;http://www.discount-air-jordan.com/ajf-6.html&quot;  rel=&quot;nofollow&quot;&gt;ajf 6&lt;/a&gt;&lt;br&gt; If its common it might be difficult to get, however, be creative and you can usually find something.</description>
		<content:encoded><![CDATA[<p>Mark S. is definitely on the right track. If you want to get a professional looking email address, Id recommend buying your name domain name, like or  <br /><a href="http://www.discount-air-jordan.com/ajf-6.html"  rel="nofollow">ajf 6</a><br /> If its common it might be difficult to get, however, be creative and you can usually find something.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: moncler jackets</title>
		<link>http://blog.jeffhui.net/2009/03/rails-and-django/comment-page-1/#comment-127</link>
		<dc:creator>moncler jackets</dc:creator>
		<pubDate>Thu, 24 Jun 2010 09:55:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jeffhui.net/2009/03/rails-and-django/#comment-127</guid>
		<description>Well , the view of the passage is totally correct ,your details is really  reasonable and  you guy give us  valuable  informative post, I totally agree the standpoint of upstairs. I often surfing on this forum when I m free and I find there are so much good information we can learn in this forum! &lt;br&gt;&lt;a href=&quot;http://www.filling-with.com&quot; rel=&quot;nofollow&quot;&gt;http://www.filling-with.com&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Well , the view of the passage is totally correct ,your details is really  reasonable and  you guy give us  valuable  informative post, I totally agree the standpoint of upstairs. I often surfing on this forum when I m free and I find there are so much good information we can learn in this forum! <br /><a href="http://www.filling-with.com" rel="nofollow">http://www.filling-with.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeffhui</title>
		<link>http://blog.jeffhui.net/2009/03/rails-and-django/comment-page-1/#comment-110</link>
		<dc:creator>jeffhui</dc:creator>
		<pubDate>Wed, 10 Feb 2010 01:27:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jeffhui.net/2009/03/rails-and-django/#comment-110</guid>
		<description>My response was too long -- see the post &lt;a href=&quot;http://blog.jeffhui.net/2010/02/djangos-flaws/&quot; rel=&quot;nofollow&quot;&gt;http://blog.jeffhui.net/2010/02/djangos-flaws/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>My response was too long &#8212; see the post <a href="http://blog.jeffhui.net/2010/02/djangos-flaws/" rel="nofollow">http://blog.jeffhui.net/2010/02/djangos-flaws/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Taylor</title>
		<link>http://blog.jeffhui.net/2009/03/rails-and-django/comment-page-1/#comment-108</link>
		<dc:creator>Brandon Taylor</dc:creator>
		<pubDate>Tue, 09 Feb 2010 18:31:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jeffhui.net/2009/03/rails-and-django/#comment-108</guid>
		<description>I&#039;m curious to know what benefits Rails provides for user-generated content?</description>
		<content:encoded><![CDATA[<p>I&#39;m curious to know what benefits Rails provides for user-generated content?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon Taylor</title>
		<link>http://blog.jeffhui.net/2009/03/rails-and-django/comment-page-1/#comment-109</link>
		<dc:creator>Brandon Taylor</dc:creator>
		<pubDate>Tue, 09 Feb 2010 18:27:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jeffhui.net/2009/03/rails-and-django/#comment-109</guid>
		<description>Coming from ASP.NET, using Rails was bliss. However, I quickly started to notice things about Rails that bothered me, starting with Rails&#039; conventions. Rails is also very monolithic. It&#039;s very difficult to encapsulate an application module such as a blog. There&#039;s so much &quot;magic&quot; in Rails that it&#039;s hard to understand what&#039;s happening behind the scenes, and the documentation, for lack of a better word, effing sucks.&lt;br&gt;&lt;br&gt;Rails has come a long way in the past couple of years, but it&#039;s JUST NOW starting to work the way Django has worked since the beginning. Encapsulating app modules, including routing, views, etc, nested forms - all baked into Django since 0.96&lt;br&gt;&lt;br&gt;Add Django&#039;s admin module and you just solved probably 95% of your use cases for editing content. It will save you an unbelievable amount of time.&lt;br&gt;&lt;br&gt;When you compare the amount of code, workflow and results, I simply don&#039;t understand why anyone would choose Rails over Django, unless you just enjoy writing admin screens, logins, file uploads, form validators and everything else Django does out-of-the-box.&lt;br&gt;&lt;br&gt;Don&#039;t let a lack of knowledge of Python stop you from getting started with Django, it&#039;s very English-like, with very minimal syntax and tons of built-in goodness. Django has the lowest learning curve of any framework I&#039;ve used in the past 13 years as a professional web developer. Python is every bit as elegant and clean as Ruby, and is a hell of a lot faster to boot.&lt;br&gt;&lt;br&gt;Happy coding!</description>
		<content:encoded><![CDATA[<p>Coming from ASP.NET, using Rails was bliss. However, I quickly started to notice things about Rails that bothered me, starting with Rails&#39; conventions. Rails is also very monolithic. It&#39;s very difficult to encapsulate an application module such as a blog. There&#39;s so much &#8220;magic&#8221; in Rails that it&#39;s hard to understand what&#39;s happening behind the scenes, and the documentation, for lack of a better word, effing sucks.</p>
<p>Rails has come a long way in the past couple of years, but it&#39;s JUST NOW starting to work the way Django has worked since the beginning. Encapsulating app modules, including routing, views, etc, nested forms &#8211; all baked into Django since 0.96</p>
<p>Add Django&#39;s admin module and you just solved probably 95% of your use cases for editing content. It will save you an unbelievable amount of time.</p>
<p>When you compare the amount of code, workflow and results, I simply don&#39;t understand why anyone would choose Rails over Django, unless you just enjoy writing admin screens, logins, file uploads, form validators and everything else Django does out-of-the-box.</p>
<p>Don&#39;t let a lack of knowledge of Python stop you from getting started with Django, it&#39;s very English-like, with very minimal syntax and tons of built-in goodness. Django has the lowest learning curve of any framework I&#39;ve used in the past 13 years as a professional web developer. Python is every bit as elegant and clean as Ruby, and is a hell of a lot faster to boot.</p>
<p>Happy coding!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->