Having developed software on both Rails and Django, I prefer the latter. Reasoning: python's community seems more professional. They have well-defined language change and enhancement processes (the PEP), good docs online, almost every question imaginable has been answered already somewhere, and the performance ain't too bad.
Plus the code smell overall is just... lesser.
Then again, I came from a background of C and scheme, and somebody on c2 wrote that python appeals to people like me more.
Having moved from rails to django development the thing I am missing the most is the wide range of mature testing tools in the ruby ecosystem. Django's testing tools feel very primitive comparatively and there's no clear separation of unit, functional and integration tests.
I'd agree that in general the python community feels more professional and that the quality of documentation is typically better.
I use Django for my projects and I don't share this opinion on the maturity aspect. Can you explain your statement a bit more? What aspects of Django are immature?
There were plenty of extensions that allowed you to use Selenium with Django, I maintained one of them. Django is fairly conservative about including new features into the core that work well as extensions. And this is something I value a lot.
The time zone support, though, was really overdue.
Not really a fair feature comparison. If db migration wasn't in Rails, ActiveRecord wouldn't work the way it does. You can't say the same about Django's ORM.
Plus the code smell overall is just... lesser.
Then again, I came from a background of C and scheme, and somebody on c2 wrote that python appeals to people like me more.