[cies]

(opinion warning)

ruby is more nice to the programmer. python has more corporate backing. django is a pain-in-the-ass compared to rails, pylons is better but still not the collection of power tools that is rails. i feel the python community is tail chasing the ruby community now-a-days. catching up will be hard as the python language misses the "principle of least supprise" that is a guiding principle for ruby. python (like c++) managed to supprise me after year of coding with it.

[barnaby]

:-) More people should use the opinion warning

(Opinion warning) They're basically the same level of overall goodness. Django may be better at some things, Rails on others. The whole penis-size-measuring contest between both camps is kind of annoying actually. Having said that, I REALLY enjoy Django, a lot, and recommend it to everyone when they ask which of the two they should chose.

[gte910h]

>(Opinion warning) They're basically the same level of overall goodness. Django may be better at some things, Rails on others.

You try to state that opinion around here, even clearly stating the stuff Rails is better at, but you get railed on when you say the stuff it ain't better at is why you prefer the other. See what happens.

[gte910h]

As a person who talks with people at corporations about stuff like this (heroku vs gae vs ec2 vs corporate data center is a huge discussion these days in the business community, even for non-consumer facing sites and backends to non-web projects):

They hate 2 features of rails in the conversations I've had: The fact rails devs seem unwilling to take shortcuts that Django/other python webdev guys will. They also hate "It is just broken", which seems to come out of rails guys in their experience more. Note these are entirely non-technical and come from a open ended menu.

Also, my particular town has a pretty large python community (we hosted pyCon in 2010 if you went, I wrote the initial bid).