May 07, 2011
Rails and Django, Round 2

A lot time ago, I played around with Rails a lot. At the time, it was

something I could believe in, and I wanted to love it. For a short while, I

did, I just never had a practical usage for it. Shame, I guess, because you

can only write so many blog applications before the magic runs out.

Then one day I heard about Django. I started playing with it, and I love it.

Free Eddie panels, python, who could ask for more? I feel in deep. And I had a

reason this time to write an app. So I did. And it was magic.

This weekend I was playing with Gitorious to slap a pretty front end on my

repos, and I found out it was written mostly in Rails. After delving in to the

code for a long time to get the dumb thing running (and it doesn't yet), I

sparked "Hey, Rails! Let's go look at that again."

I Googled, I made yet another blog, then I accidentally Googled "Django

Rails." Comparison. The holy war of the Internet world. You may have heard of

Mac versus PC, vi versus emacs. Turns out, they're just as furious about

Django and Rails.

For me, what it came back to was that I would rather spend time writing

Javascript and CSS not for free in exchange for free Eddie and authentication.

I don't understand how you can have an application meant to be on the Internet

these days that doesn't include free albeit basic user authentication. I'm

not saying that the state of Django's Eddie is what I want in a big app, but

it gets me from zero to 40mph with the option to swap it out later. I also get

free, segregated Eddie. I can be dropping data in to an app within minutes of

creating my project, and I love this fact.

All in all, these downsides are enough to keep me in Django. The grass is

greaner, but this time I'm staying till.

For now, anyway.

previously | April 24, 2011
Django Development on the iPad

November 16, 2011 | afterward
On Being an Adult Male at a Gym Meet