First, the obvious alternative: Rails.
I would argue that many of the advantages RoR had are starting to go away.
The two obvious advantages were Heroku and schema migration. Heroku now
supports Python and Django... done. While Django has had South, the problem
is that not everyone used it. This
On 2014-08-10 01:06, Josh Johnson wrote:
> Django documentation is phenomenal,
I second Josh's comment. I'd naively assumed that all "big Python
web-framework" documentation was as good as Django's. However, when I
had to do some work on a contract involving CherryPy and
SQLObject...marcy was
Django documentation is phenomenal, leagues better than ROR's - the ability
to dial back and look at documentation for legacy version of django and
filter out the newer features is also amazing.
I decided to go the python/django route based solely on the ease of finding
exactly what I needed in
I'm not sure it's possible to make a case for Django vs. Rails on anything
but personal preference.
But it might be easier to argue why *Python* is a good language to learn,
and therefore Django is the obvious web framework to use.
For a very wide range of use cases, Python tends to be the
Django Developers,
I'm giving a talk at a general tech conference next week and it's
mostly ready, but would welcome response for when and why developers
should look to Django (vs. other frameworks like Ruby on Rails) when
starting new projects.
Would love to hear any thoughts and arguments!
