INTERESTING QUOTES: '... although there is no reason why fastcgi couldnt be used ...' ~ except it's slower! ~ http://superjared.com/entry/quick-django-benching. '... here is no equivalent of a model-specific SQL refresh something that could drop a specific models tables and regenerate the needed SQL automatically ...' ~ true, recognised & being corrected ~ http://www2.jeffcroft.com/blog/2006/jul/20/top-ten-things-suck-about-django.
SOME POINTS: Two things come to mind that are not mentioned. The first is hosts. What is the comparison between hosts? The second is how mature the language is. If I want to use python and I need a particular module that does 'fo '. it is probably out there somewhere (though it may be alpha or beta it will most likely out of date) unless you want to re-invent the wheel. I can't say the same for Rails. Ruby is just a younger language with less code mass.
QUESTIONS TO ASK: In the end what really matters is how good the idea & business is. There are plenty of Rail based companies I can think of making a go of it. The same applies to Python based companies. If you accept that technology is an amplifier of ideas, will using Rails or Django alone make a better choice? Is the difference between them compelling enough to make a difference? One area that could tip in Rails favour is "susinctness". But Django with it's python code base has more tools to choose from.
INTERESTING QUOTES: '... although there is no reason why fastcgi couldnt be used ...' ~ except it's slower! ~ http://superjared.com/entry/quick-django-benching. '... here is no equivalent of a model-specific SQL refresh something that could drop a specific models tables and regenerate the needed SQL automatically ...' ~ true, recognised & being corrected ~ http://www2.jeffcroft.com/blog/2006/jul/20/top-ten-things-suck-about-django.
SOME POINTS: Two things come to mind that are not mentioned. The first is hosts. What is the comparison between hosts? The second is how mature the language is. If I want to use python and I need a particular module that does 'fo '. it is probably out there somewhere (though it may be alpha or beta it will most likely out of date) unless you want to re-invent the wheel. I can't say the same for Rails. Ruby is just a younger language with less code mass.
QUESTIONS TO ASK: In the end what really matters is how good the idea & business is. There are plenty of Rail based companies I can think of making a go of it. The same applies to Python based companies. If you accept that technology is an amplifier of ideas, will using Rails or Django alone make a better choice? Is the difference between them compelling enough to make a difference? One area that could tip in Rails favour is "susinctness". But Django with it's python code base has more tools to choose from.