Also, they have (or had, at the time) completely different philosophies: while Rails was highly tied to "convention over configuration", Django went the other w

Also, they have (or had, at the time) completely different philosophies: while Rails was highly tied to "convention over configuration", Django went the other way after the "magic removal" branch and it became fully "configuration over convention". When I had to chose one over the other, I ended up using Django simply because diagnosing issues was simpler. Rails required a pretty substantial amount of a-priory knowledge to get things started (think, naming a file or method a certain way for it to magically be available somewhere else.) Django was more straightforward and allowed you to write code that, while not 100% django-esque, would work. I remember doing a lot of refactoring whenever I'd figure out a new framework idiom that I had missed earlier, but hey... I had working code before I needed to learn the idiom.