The Web Squeeze: Django Vs Rails - The Web Squeeze

So, as far as I understand it both are about the same but in different languages. I am going to learn one of the two. Does anyone know the key differences between the two frameworks?

The differences are substantial but the the differences are also quite small

Django is a Python framework and Ruby on Rails is, suprisingly enough, a Ruby framework.

Before looking a the frameworks themselves it's probably good to consider the languages behind them. Python is the older language having originally been released in 1991 and Ruby was first put out to the public in 1995. This makes both Python and Ruby quite old in terms of programming languages and as they are both Open Source, they have a committed and enthusiastic community supporting them.

Ruby resembles Python in many ways in both syntax and programming procedures and both languages are completely Object Oriented. Every variable you create or use is simply a reference to an object. This also means that variable typing becomes an issue in both languages with varibles requirind conversion before being used as a different data type (an integer needs to be converted into a string before you can concatenate it to the end of a string literal). For me, this was one of the harder things to grasp coming from a large experience with loosley typed languages like PHP and Javascript. Python also uses whitespace in its syntax which confused the hell out of me originally before realising that this is a very good thing. When writing an IF statement, the next line must be indented. This makes for great readability in the script and a lot less curly braces.

Now, the frameworks themselves starting with the similarities:

• As is the case with most server-side web frameworks, both Django and RoR implement their own versions of the (Model, View, Controller) MVC method of project development. This is a popular Object Oriented approach whereby the Model (data, usually dynamicall created based on the database being used in the application) is kept separate from the View (What the end user sees) which is also kept separate from the Controller (The object methods that process and manipulate the Model before passing to the View). Django uses a slightly different naming convention renaming the View to template and the Controller to View essentially implementing the (Model, Template, View) MTV. In a nutshell the development is the process of creating some class Models and pointing them (or having the Framework create and then point them in the case of Django) at the database that their properties will be filled by, writing the Controller logic that processes that data and loading the processed data into the view for display.
  
• Both frameworks are great for rapid development taking the lower level operations out of your hands and letting you write the high end logic
  
• It is hard to find hosting that supports them. Usually a host with Ruby &/or Python is more expensive as it takes a slightly more advanced knowledge to set up (you won't get Ruby or Python on a $10 a year package -- if you can though let me know )

That's a small set of the similarities, now for some of the differences.

• RoR takes many fewer lines of code as it is a very "magic" framework that uses assumptions and specially created logic to help you out.
  
• RoR is a little faster to deploy, getting Django running remotely on your host can be a touch trickier
  
• From my view, RoR is less portable. Django enforces an app/project approach. You have a project, but within that you have many smaller applications. These applications are self contained little programs that can be picked up and dropped in somewhere else. Because of this there are many, many useful pre-written applications that you can include into your own without having to change a line of code.
  
• Django has, quite simply, the best dynamically created administration panel I have seen in any framework. The whole admin backend is created on the fly in Django giving you a quick interface to fill your site with content. You can of course customise is easily with a few lines of code in your Models.
  
• Django's documentation is impeccable. If you find an error or something missing you should probably win a prize. If that's not enough the Django userbase is almost fanatical in their support for the framework sometimes to the point of intimidation for newer users but such dedication is very useful.
  
• Ruby's documentation is also fantastic with a large use of screencasts and videos to introduce new users. I haven't had much to do with teh Ruby community but I assume that they are as avid as Django's

From where I stand, I am currently loving Django but I would dearly love to give RoR a harder workout if only my host supported Ruby. As to which is the better framework? I think that this is one of those questions that cannot be answered. I reserve my judgement indefinitely because both offer many possibilities.

You can set both Django/Python and RoR up on your linux, windows or mac box so I recommend burning through a couple of tutorials in each to see how you like them.

Hope I helped a little.

Thanks a lot. That is very interesting. I am going to be learning RoR but before I started I wanted some idea on what I would be missing out by ignoring Django.

It was as I suspected. Both are very similar albeit them using different languages. The differences are somewhat minor. The portability is definitely a plus point for Django but I have sampled RoR magic and my face lit up with delight. Based on what you have said it seems very much down to personal preference.

Site5 supports both Python (So I assume that means Django as well) and RoR if you are looking for a webhost. If your quick you can get it for $5 a month.