|
|
|
|
The Rails Way is to be concise and use dynamic code.
The Python Philosophy is to be explicit.
|
Validity:
95%
|
|
Rails is written in Ruby.
|
Validity:
93%
|
|
Rails has many built-in helper functions for AJAX support using the Prototype and Scriptaculous libraries.
Django has little built-in AJAX support, leaving the choice of Javascript libraries and frameworks up to the developer.
|
Validity:
90%
|
|
Major websites and projects using Rails include Basecamp, Twitter, and Yellow Pages.
Major websites and projects using Django include washingtonpost.com and chicagocrime.org
|
Validity:
86%
|
|
Rails has no built-in admin system, but there are several plugins which can provide the functionality.
Django comes with a full-featured, built-in admin system.
|
Validity:
82%
|
|
Rails uses migrations to evolve the database schema.
At the moment, Django does not have a built-in mechanism to evolve the schema.
|
Validity:
81%
|
|
Rails uses the database schema to determine the attributes of the models.
Django uses the attributes defined in the model to generate the database schema
|
Validity:
77%
|
|
Rails uses the powerful eRb template language, allowing for complex code in the templates. Plugins allow the use of Liquid templates as well.
Django uses a simpler, designer-friendly template language
|
Validity:
66%
|
|
pending review
frameworks come and go. long term success is based on the language. ruby is a bad copy of python.
Python is the reason to choose Django. Much more mature, capable, easier to scale. Invest in python.
|
Validity:
30%
|
|
pending review
Ruby ain't a bad copy of python, more like a bad copy of smalltalk.
Python is a bad copy of Ada
|
Validity:
14%
|
|
pending review
rails suck ass
|
Validity:
8%
|
|
pending review
Rails rules
No clue about Django, never used it
|
Validity:
8%
|
|
Add my point
(No sign in required!)
|
|
|
|
|
|
|
