I recommend giving Django a try, if only to see how it feels to you. I think that the major factor on deciding between the two is how easy it is for you to use, especially in my case. There happened to be a lot of things leading me to Python, so that may have helped push me toward Django some, too. It kind of felt like Rails was pushing me to do one thing when I expected another, and that might just have been the fact that I was less experienced with MVC frameworks in general.

I’ve found a few examples of how to integrate Django with AJAX, but they’re not as easy to follow (or as plentiful) as the Rails examples. I realized coming in that it wouldn’t be as easy, but Django does let you choose your own JavaScript library, so maybe that’s good in the end. Deployment seemed to be easier with Django, but that might also be because I’m more familiar with the environment on which I was deploying it.

So basically there are tons of factors, but since in my case I got to choose whichever I was more comfortable with and I don’t have any outside pressure to choose one over the other, I think I’m going with Django.

The quotational site looks pretty cool, I’ll be curious to see how you implement the “Submit your favorite quotes” addition. Does django provide any built-in support for JS/AJAX libraries? If so I could see you doing some cool live search / filter / sorting tricks.

I’ve been meaning to try out django one of these days before I get to deep into Ruby on Rails (I’m already using Rails for a couple of projects at work). Just curious, what advantages have you found django has over Rails?

-Joe