Ian Bicking: the old part of his blog

Re: What Really Makes Rails Work

QMTest is another example of a system that brings people to python (it's what brought me - starting from "there's got to be something that kills DejaGnu out there, oh look, QMTest might be it" and learning enough python to hack tests ("wow, this sucks so much less than TCL! it actually has quoting!") and then coming upon a reason to use Python instead of perl, since it was at hand, and bootstrapping from there... but again, the batteries mattered as an enticement more than the language did. It took something like a year for me to really decide the language was a winner.)

As for ZOPE - it has traditionally been positioned as solving a problem I don't want to have :-) This means I've been able to recommend it to IT types and nod positively about it when it comes up in content-oriented rather than engineering-oriented contexts, but it's very much got a "them not us" feel to it. I think that has a lot to do with why it isn't talked about as a "unversal" framework - it doesn't scale down to the individual python hacker trying something clever, if they're not already swimming in it.

Comment on What Really Makes Rails Work
by Mark Eichin