Although it’s not exactly what Jason is saying in his post, I think the spoon/jackhammer comparison applies even more directly to agile web app framework versus monolithic Java environment discussion. Rails is their spoon. And if Rails is a spoon, Django is a spork. :)
http://www.37signals.com/svn/posts/230-a-spoon-or-a-jackhammer
001 // Baxter // 01.26.2007 // 3:28 PM
If it’s a spork, it’s this lightweight titanium version: http://en.wikipedia.org/wiki/Image:TitaniumsporkHorizontal.png
002 // Arik // 01.27.2007 // 12:50 PM
lol. You’re really adamant about Django being better than rails aren’t ya?
003 // Jeff Croft // 01.27.2007 // 1:24 PM
Not seriously, I’m not. :)
I’ve never used Rails, so aside from what I’ve read, I don’t have a very good base of information to use as a comparison. I have fun with some pointed comments like this one, but it’s definitely all good-natured and just for kicks.
Although I’ve not used Rails, my impression is that it’s a great framework, and totally deserving of the hype around it. The truth is that Rails, Django, and most of the other rapid application development frameworks that have been popping up have far, far more in common that they do differences. They’re both intended to address the same issues, and they both seem to do the job quite admirably.
I’m a Django fan. Just like I’m a Kansas City Chiefs fan. You’ll hear me say, “Chiefs rule! Chargers suck!,” sure. That’s what fans do. But, deep down, I know that the Chargers are every bit as good as the Chiefs (or better, in that case!).
Rails is a great framework, no doubt. But it does have a lower cut-off point as for features. There are several things that Django handles at the framework-level that Rails doesn’t. This is a conscious decision on the part of the Rails team, and that’s fine. BUt that’s why I said Django would be a spork to Rails’ spoon. It’s a similar device that does a few more things. :)