Constructive reasons to use Django instead of Rails

Why is a two-year-old article being posted now? EDIT: Sorry, should've added: Especially in a domain that changes so quickly? Both Django and Rails have grown immensely since this was last updated.

"One such instance that led me to using Python over Ruby was my need of a DBF reader. You can't find this anywhere for Ruby, but I found a very solid implementation in Python that I was able to plug right in."<p>Oh really ? <a href="http://www.google.com/search?q=ruby+dbf" rel="nofollow">http://www.google.com/search?q=ruby+dbf</a><p>This sort of compromises the credibility of the whole article in my opinion.

We're busy porting Pootle (translate.sf.net) to Django and it's painful. Webapps don't seem to be Django's strong point (though I'm sure that it excels in other arenas).<p>I've only played with Rails before, but I get the impression that it's far more suited to the kind of thing we're doing.