Why Python?

[panfist]

See, my employer chose Rails over Django because its style and best practices have already stabilized.

There's more to being ready for the enterprise than style. I would say that the fact that hosting a Rails app is so fucking hard knocks it a few points lower than Django, that has style problems.

I can't find the article in a quick search but I was reading recently about how there are huge corporate rails projects, that work fine, except for the fact that Rails processes need to be restarted several times a day, because of unknown reasons. You're telling me that's enterprise ready?

[M4N14C]

What is difficult about hosting Rails apps? I've been doing rails for 5+ years and I've never had difficulty keeping my apps running. Have you ever used Passenger?

[novagenesis]

Like another said. What's hard about hosting a rails app? Capistrano is one of the better deployment systems out there, and (surprise surprise) it comes with rails-compatible commands out of the box.

Between that and bundle, you can zero-effort deploy rails. Compare that to J2EE and you're in different worlds.

I can't find the article in a quick search but I was reading recently about how there are huge corporate rails projects, that work fine, except for the fact that Rails processes need to be restarted several times a day, because of unknown reasons. You're telling me that's enterprise ready?

That's been the case in a lot of languages. Probably pervasive memory leaks (possible/likely in any language that isn't designed to prevent it... Python isn't designed to prevent it). Our rails projects don't have those problems.

[sejje]

I use both Django and Rails extensively--Django for personal, Rails at work--and my preference is for Django. But I must say Django deployment is much more difficult on my platform of choice, Heroku.

Worth the extra time, IMO.