Ray wrote: > Steve Holden wrote: > >>I wouldn't waste your time. "A man convinced against his will is of the >>same opinion still", and they already know they aren't interested in >>Python. There are probably many other matters about which they are >>uninformed and equally determined. > > > Well the thing is that I have to admit I have some stake in this. If > we're using Rails then everybody's starting from 0. Whereas if we're > using Python I already know it so I'll have an easier time :) > > Also, those are just two developers. Convincing the big guy, the > decision maker, is a separate matter isn't it? > > Do you know of any other arguments, or you do think that for somebody > who really, really doesn't care about which language, either RoR/Ruby > or Django/Python will do just fine? > Well, my view is that both are frameworks, and so you will inevitably "run out of steam" at some point if your implementation plans become too ambitious. The impression I get is that Rails is relatively inflexible on database schemas, and once you get "off the beaten track" it gets difficult to cope with complex existing databases.
regards Steve -- Steve Holden +44 150 684 7255 +1 800 494 3119 Holden Web LLC/Ltd http://www.holdenweb.com Skype: holdenweb http://holdenweb.blogspot.com Recent Ramblings http://del.icio.us/steve.holden -- http://mail.python.org/mailman/listinfo/python-list
