Comments on: Magpie’s Django / Rails comparison http://lesscode.org/2005/08/16/magpies-django-rails-comparison/ AAaaaaahhhhrrrrrrr! Mon, 17 Sep 2007 09:12:45 +0000 http://wordpress.org/?v=2.0.1 by: Jeff Wood http://lesscode.org/2005/08/16/magpies-django-rails-comparison/#comment-252 Sat, 20 Aug 2005 17:28:52 +0000 http://lesscode.org/2005/08/16/magpies-django-rails-comparison/#comment-252 <p>Uh? I still don't get it... Everybody compares everything to Rails ... Rails is great for a limited space ... People need to look at Nitro ( http://nitrohq.com ) I didn't see anything in Django that Nitro doesn't have, and comes with Ruby syntax.</p> Uh? I still don’t get it… Everybody compares everything to Rails … Rails is great for a limited space … People need to look at Nitro ( http://nitrohq.com ) I didn’t see anything in Django that Nitro doesn’t have, and comes with Ruby syntax.

]]> by: Sam Newman http://lesscode.org/2005/08/16/magpies-django-rails-comparison/#comment-204 Tue, 16 Aug 2005 17:35:18 +0000 http://lesscode.org/2005/08/16/magpies-django-rails-comparison/#comment-204 <blockquote> <p>Rails is, of course, not limited to AJAX-heavy apps with simple domain models. I’m assuming Sam didn’t mean to give that impression but was just trying to wrap up a long article quickly. Perhaps he’ll clarify a bit.</p> </blockquote> <p>Argh! You know me too well. Yes, what I really wanted to say is that both Django and Rails have their sweet spots, they overlap to an extent, and that if you're not sold on either Ruby or Python yet you should pick the one closest to your sweetspot. Doing a Backpack-style web 2.0 application? Go Rails. Doing a more passive large-scale portal-type site? Go Django. What to make a web 2.0 app in Django? <a href="http://www.chicagocrime.org/" title="Chicargo crime.org" rel="nofollow">Go ahead</a> - although Rails might give you more for it out of the box. Want to do a big portal-style site with Rails? I'm sure that's possible too - Django just might like it a bit easier.</p>

Rails is, of course, not limited to AJAX-heavy apps with simple
domain models. I’m assuming Sam didn’t mean to give that impression
but was just trying to wrap up a long article quickly. Perhaps
he’ll clarify a bit.

Argh! You know me too well. Yes, what I really wanted to say is that both Django and Rails have their sweet spots, they overlap to an extent, and that if you’re not sold on either Ruby or Python yet you should pick the one closest to your sweetspot. Doing a Backpack-style web 2.0 application? Go Rails. Doing a more passive large-scale portal-type site? Go Django. What to make a web 2.0 app in Django? Go ahead - although Rails might give you more for it out of the box. Want to do a big portal-style site with Rails? I’m sure that’s possible too - Django just might like it a bit easier.

]]>