My memory is not altogether clear, but I seem to remember that Django felt a bit biased to very content-centric apps, that being where it came from. I didn’t spend a lot of time with Django.

I did spend a reasonable amount of time with TurboGears, and to be frank it was fairly painful. There was a user management component being added, and I needed it, and it caused me all sorts of trouble – always trying to do too much – to force me into a model I didn’t want.

Switching to Rails was like a breath of fresh air. It hit the sweet-spot of making things quick and easy, while leaving me to make the decisions about how I wanted my app to work. Convention-over-configuration won me over instantly.

Since then I’ve realised one important thing – when you pick a technology, where it’s headed is just as important as where it’s been. TurboGears seemed to have a disorganised culture with no strong direction. Rails otoh is guided by some very smart people making some very smart decisions. So overall I’m very happy I switched.

I do look back over the fence from time to time though, and think hmmmm. Pylons looks very interesting, and SqlAlchemy seems like it might be a very important retake on the idea of ORM. I haven’t looked closely though.

completely off topic. As you are a veteran python dude why did you decide to go with rails instead of django? Sorry it has nothing to do with hobo or rails..i just want to know why ruby and not python.. i know there are many many sources debating this issue.. i just want to hear tom’s view.

so if we can do less with rails, and even less-er with hobo, then maybe we’ll have time to focus on things that really matter? like aesthetics and enjoying our lunch or a glass of wine instead of speeding through the good things so we can do the repetitious mundane things at a faster pace?

I’m all for slow baby!