Define "real". Like I told you, it doesn't bother me.
> Migrations were something that SO many people wanted
You are right - and we had South for it and we used it a lot. Integrating South into Django's core was not a trivial effort, however, but, again, since we already had South, it was not a big issue.
> That is 14 months and $30,000 to get a feature into the framework while already having a tested and battle hardened implementation as a third party module.
IIRC, the 30K were paid to the third party who created South to build a better migration engine it into Django. You can continue to use South for as long as you want. It's just that, starting with 1.7, you'll get migrations built in and South will no longer be required.
I still fail to see why do you think everybody has to be concerned with the problems you find important. If it bothers you so much, then solve it.
edit: corrected the character of the effort
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.
Do you not see the bigger picture? The runserver problem is only 1 thing. People are expecting to be fed tens of thousands of dollars through kickstarter to create features that people want instead of the core django devs implementing them.
The reason why rails has an amazing development experience has nothing to do with rail's API or ruby.
It's because rails is extracted and built out of a product that some of the core devs work with 24/7 (basecamp). They add useful things like a development server that isn't garbage because they work with it on a daily basis full time.
I don't want to see Django fall over because they don't add any features that people actually want and instead force the community to beg for money on kick starter to do it.
You are expecting developers to adapt the amazing software they made (for free) to your needs and do all that immense effort for free. You see your problems and think they should be everyone else's top priority. Should they thank you for pointing The Way?
You have to understand the world does not revolve around you.
Django is free as in freedom. You have the freedom to modify it to your needs. Use it.
Having to throw up kick starters for every feature is unreasonable.
Migrations were something that SO many people wanted and the core devs didn't even think to add it. It had to be merged in by a random person in the community for $30,000 and it also took 14 months assuming Django ships 1.7 in May going by their roadmap.
That is 14 months and $30,000 to get a feature into the framework while already having a tested and battle hardened implementation as a third party module.