There’s always been a debate between which is better to use, Django or Ruby on Rails. Although, the two are pretty much different with each other, their similarity is visible and comparing the two is inevitable. Before we declare a winner between Django and Ruby on Rails, let’s first know the two platform better (I tried them both using a godaddy coupon 2011 list for a unique name.)
Django emerged as a product of the highly successful Lawrence Journal World and was intended to host news site. On the other hand, Ruby on Rails sprouted from the development of Basecamp as a framework for a project management web-based service. Considering that both framework is an output of a development of a web-based application then we can conclude that its objectives during its developmental cycle are its strongest feats. News sites for Django and Project Management by Rails. Although it is a correct notion, the two frameworks are more than what they were originally intended to be. Their architecture is now robust that they can be used in almost all types of web applications.
The two frameworks uses HTML templates as its physical architecture. The major distinctions is in their formats which the Rails uses an inline Ruby codes for the templates while Django applies its own templating tag language. In this case, Rails functionality can be extended into complex functionality which Django may lacks but Django is simple enough that users with lesser programming skills can still develop web applications and templates.
It is not really necessary for us to declare a winner for both frameworks are doing well to its base platforms and has started a strong of community of supporters. But if I have to choose, I would proclaim Django since it has Jython and AJAX supports so it means a cross platform compatibility between Java and AJAX… and that is a rare feat for CMS.