<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: My experience with Django and Rails</title>
	<atom:link href="http://scottmoonen.com/2009/01/09/my-experience-with-django-and-rails/feed/" rel="self" type="application/rss+xml" />
	<link>http://scottmoonen.com/2009/01/09/my-experience-with-django-and-rails/</link>
	<description>Jesu, Juva</description>
	<lastBuildDate>Wed, 03 Feb 2010 15:16:30 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brandon</title>
		<link>http://scottmoonen.com/2009/01/09/my-experience-with-django-and-rails/#comment-421</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Wed, 03 Feb 2010 15:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fullvalence.com/?p=48#comment-421</guid>
		<description>Coming from .NET, Rails was bliss. Ruby is very pretty and has some very nice features, but 99% of the sites I build need an admin, and I hate writing admins.

First of all, I think both frameworks are good. However, what I discovered through my experience with both frameworks over two years, is that what Rails had in hype, Django had in substance.

I found that I could accomplish tasks faster, with more portability in Django than I could in Rails. Django&#039;s admin gets me 99% of the way there with most projects, and that single app module alone has saved me months of development time and greatly streamlined the process of administrating data and permissions.

Django&#039;s application structure and url patterns are highly modular to begin with. I can pull in apps as an svn:external, add the app to my installed applications, add the url patterns (2 lines of code total), sync my db or run the South migrations, and I&#039;m up and running. Yes, you can write plugins in Rails, but it&#039;s not the same.

I feel that Django&#039;s ORM is just as or more powerful than ActiveRecord, with very clean syntax. Q objects make it very simple to create highly complex queries.

Django&#039;s template system, while spartan in appearance, is much better in my opinion than allowing the embedding of pure Python or Ruby code in templates. You&#039;re forced to encapsulate, and it makes for highly portable code. If you&#039;re a Django developer and haven&#039;t looked at writing template tags or inclusion tags, do so today.

Django&#039;s popularity is reaching a tipping point, and I&#039;m getting more and more calls from recruiters looking for Python/Django people.

In 13 years as a professional developer, it&#039;s the most well-conceived framework I&#039;ve used. It put the fun back in development for me, and saves me a lot of time. I&#039;ll get on my soapbox for Django any day against Rails, .NET or PHP.

My $0.02.</description>
		<content:encoded><![CDATA[<p>Coming from .NET, Rails was bliss. Ruby is very pretty and has some very nice features, but 99% of the sites I build need an admin, and I hate writing admins.</p>
<p>First of all, I think both frameworks are good. However, what I discovered through my experience with both frameworks over two years, is that what Rails had in hype, Django had in substance.</p>
<p>I found that I could accomplish tasks faster, with more portability in Django than I could in Rails. Django&#8217;s admin gets me 99% of the way there with most projects, and that single app module alone has saved me months of development time and greatly streamlined the process of administrating data and permissions.</p>
<p>Django&#8217;s application structure and url patterns are highly modular to begin with. I can pull in apps as an svn:external, add the app to my installed applications, add the url patterns (2 lines of code total), sync my db or run the South migrations, and I&#8217;m up and running. Yes, you can write plugins in Rails, but it&#8217;s not the same.</p>
<p>I feel that Django&#8217;s ORM is just as or more powerful than ActiveRecord, with very clean syntax. Q objects make it very simple to create highly complex queries.</p>
<p>Django&#8217;s template system, while spartan in appearance, is much better in my opinion than allowing the embedding of pure Python or Ruby code in templates. You&#8217;re forced to encapsulate, and it makes for highly portable code. If you&#8217;re a Django developer and haven&#8217;t looked at writing template tags or inclusion tags, do so today.</p>
<p>Django&#8217;s popularity is reaching a tipping point, and I&#8217;m getting more and more calls from recruiters looking for Python/Django people.</p>
<p>In 13 years as a professional developer, it&#8217;s the most well-conceived framework I&#8217;ve used. It put the fun back in development for me, and saves me a lot of time. I&#8217;ll get on my soapbox for Django any day against Rails, .NET or PHP.</p>
<p>My $0.02.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
