The migrations project was a re-write, not an integration with South. Common misconception, but the new migrations implementation is actually better than South's.
That's disgusting...
To go back to your original question, of is Django pay for features, I don't know enough about it. But one place you could look into is the amount of corporate support Django gets. Maybe Rails has enough corporate support + people who want to work on Rails in their free time in order to get the features, versus Django. Sometimes you need to pay people to work on open source projects and the crowdfunded thing is just more visible than the corporate employees.
Stop hiding.
You can accuse me of down voting you but you're accusations are misplaced. I wouldn't waste my time. How about you go ask the site owner to check who down voted you.
I will bet my life that it's not associated to my IP address or this account. Go troll someone else man and lay off the insults, it makes you look like you're a child.
Why should I believe it?
BTW, an SSD would be much cheaper than paying for someone else to solve your problems.
Even compiled languages like Go using non-trivial frameworks (Revel) reload faster than django's runserver. It's like django's runserver is still in 2007 while everyone moved on years ago.
I'm also not the only one who isn't happy with the speed because right now runserver polls for updates every second. Some core dev implemented a change so that it's push based now instead of polling every second and should be in 1.7, but this only happens if you have pyinotify.
Want the know the kicker? The ticket to do it was opened 5 YEARS AGO.
https://code.djangoproject.com/ticket/9722
That's only a small gain though but it's crazy to think that it's been polling this whole time. I'm all for polling in web apps when possible but seeing a comment you didn't know even exist pop up 3 seconds after it was made is much different than expecting immediate feedback when you spend ~60 hours a week developing a web app.