Constructive reasons to use Django instead of Rails (Proxied)

« Auto Adjusting Pagination As A Template Tag Plus Include | Home | Easy Fix: Mysql InnoDB: Database was not shut down normally »

Constructive reasons to use Django instead of Rails (Proxied)

By Paul Kenjora | January 9, 2008

I stumbled across a gem of an article on Dzone today. The article is a very good comparison of Django and Rails without diving into too much detail or bashing. It helped me phrase some of my arguments for and against Django vs. Rails. I thought I’d share with the community. Here is an excerpt:

"Browsing around the wonderful programming.reddit.com last night, I came across a post titled Why Django kicks Ruby on Rails’ collective ass. This is an interesting article, mainly because in a sense it is right, but it goes about explaining Django’s benefits all wrong. First of all, Ruby on Rails ain’t plural, and therefore it cannot have a ‘collective ass’. Ok, I kid. But seriously, I started out my web programming ‘career’ with Rails, and I have since moved over to using Django. I’ll try to list some constructive reasons why the ‘pragmatic’ (buzzword!) developer would chose Django over Rails." – jp’s domain

The full article can be found at the link below:

http://jesusphreak.infogami.com/blog/why_django