They're both great frameworks. Most of the complaints I had about Rails have been addressed by the upcoming Rails 3. If you're learning Rails for fun, you mig

They're both great frameworks. Most of the complaints I had about Rails have been addressed by the upcoming Rails 3. If you're learning Rails for fun, you might as well start using the Rails 3 beta since there are tons of new goodies in it. Network effects are very important for these kind of things, so I'd recommend checking out local user groups for both languages/frameworks to see where you'd fit in best. It seems a good deal more people in my town (Portland, OR) are familiar with Rails than Django. Anecdotally, while there are more Ruby/Rails developers around, their average proficiency is lower than Python/Django devs. Also, the culture surrounding each framework has a different vibe. I don't want to draw too many generalizations, but in my personal view differences in culture do exist. Getting to know other developers who use both tools should be an important part of picking which language/framework to use. Or, learn to use both. It'll be good for you. Knowing the strengths and weaknesses of each language will make you a better developer, and reduce the chance of you becoming an--excuse the term--ignorant zealot.