[Django]-Feature differentiation: Rails / Django

by

0👍

✅

My experience/opinion is that Rails is much more flexible and has a more diverse ecosystem and is developing faster while Django is more stable, slower changing, better documented.

Rails has a huge advantage for integration with other systems via JRuby. You can give rails access to the entire Java ecosystem and run it on the JVM.

Django might be able to take advantage of .Net via IronPython (I don’t know anything about this other than that IronPython exists – while IronRuby is only on the way but not here yet)

👤srboisvert

11👍

Django on Jython is running nicely so Java integration shouldn’t be a problem.

In terms of integration in general don’t forget that Django is also Python so you have the massive support of the standard library plus all the other mature well supported Python projects out there. Integrating 3rd party Python code into Django projects is usually trivial.

At the risk of getting evangelical I would list the following Django killer features:

  1. The admin
  2. The documentation
  3. Python 😉
👤Andy Baker

3👍

Django also has GeoDjango. The NY Times chose Django over Ruby for their Represent project for easy mapping support:

“We built Represent with Django, the Python web framework. Although we do most of our work with Ruby on Rails, we chose Django for this project so we could use GeoDjango, an add-on that supports geometry fields and extends the ORM to allow spatial queries.”

👤Doug

Leave a comment