As for the post, very nice writeup! I largely agree with everything here, even thought I’m a Rails guy. I’d add a couple more wins for Django: The admin is a very slick feature, and I absolutely prefer the templatting language vs. erb, which invites all sorts of problems. Of course you can emulate both with various Rails plugins, but that’s not the point here.

On the Rails side, I think ActiveRecord is a far, far, far better ORM in general, and Rails 3 promises to vastly improve things further by allowing the ORM to be completely swappable.

Django is faster than rails, but please check your informations before writing

http://guides.rubyonrails.org/2_2_release_notes.html#thread-safety – it has been released about a year ago.

Django is significantly faster than Rails. It also uses significantly fewer memory. A Rails process typically can be around 100MB, while a Django process is more like 20MB. Django can be run in multithreaded mode, so you can have 5 threads in a 30MB Django process vs. 500MB for 5 Rails processes.

This means that with Django you get a bigger bang for your buck spent on hardware. If you have a $20 256MB VPS that needs to run Linux, Apache, Django or Rails, and MySQL – with Rails youwon’t be able to serve more than 1 concurrent user while with Django you can serve 5 or 10. Same if you have a 8G dedicated server – you can serve far more concurrent users with Django than with Rails.