Rails vs Django
So it’s worth reading The performance test of 6 leading frameworks though I found it lacking. The methodology is so far removed from a real world scenario that it’s hard to be swayed by the numbers. The results were that Django comes out first in performance, followed by TurboGears and Ruby on Rails 1.1.6. Besides the lack of a real world scenario I also wonder about caching. I know Rails has no caching by default but I have no idea about the other frameworks. And not only that, Rails by default runs in development mode which is much slower due to the additional debugging information and the checking to see if classes have changed (no class caching). However, it would not surprise me if Django was indeed faster just as python is faster than ruby. And I like Django, the little that I’ve used it. I like the speed, I like python, I like the templating, I like the admin. But here’s why I’m going to stick with rails: database migrations, ferret (lucene port) for searching, larger user base (at the moment), unit testing, nice separation of development vs production environments and tools for moving between them. And certainly these strengths and weaknesses have been noted before. But the other issue that the framefwork comparison raises is that Rails 1.2.1 seems much slower than 1.1.6 which is certainly something to investigate.
0 comments so far
"Rails vs Django" was written on February 4, 2007 and filed in all, ruby on rails