Re: A Rails/Django Comparison

[David Sissitka]

Performance is definitely a factor, but do you think that it has a place in this article? There are so many ways to deploy a Rails application, which would you include? A book has been written on the subject, covering even half of them in little detail would easily double the article in size. :P If you're going to include works in progress then it's also worth mentioning that the Rails documentation drive has collected over $16,000 USD for professionally written documentation. Just trying to keep things even.

-David Sissitka

On 11/14/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:

On 11/14/06, Angel García Cuartero <[EMAIL PROTECTED]> wrote:
> I found that most comparisons just don't talk about performance. It would be
> great to check how both frameworks deal with complex projects, not just Tada
> Lists... you know what I mean. :)

Yes. Performance. This article deliberately skims over performance,
but I'd suggest that's an important factor in people's decisions.

Another factor: the amount of good documentation. Rails has books that
cost money and skimpy free documentation, whereas Django has no
commercial books (yet) but fantastic free documentation, plus a free
book that's in the process of being finished ( djangobook.com). Dozens
of people have told me this is a key Django advantage in their
experiences.

Adrian

--
Adrian Holovaty
holovaty.com | djangoproject.com

--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---