On 10/16/05, william@opensource4you.com  wrote:
> But if I summarize the context of Quixote, we can find
> - a wiki
> - writings (check those of Mike Orr)
> - documentation (check those from Titus Brown, Dave Kuhlman, ...)
> - well known site suing it (LWN.net)
> - a mailing list
>
> Thus the means are there to meet more Python users/developers, no ?

Absolutely. There are a lot of bright people on the quixote-users
list, and they're mighty friendly too. :-)

> Thus what's missing for Quixote to have a bigger community size ?

These days, I'd say it needs a 20-minute how-to video; that seems to
be the current craze. Or it needs to be folded into a larger
framework, as TurboGears has folded CherryPy, SQLObject, etc.

The problem with the 20-minute video is that there isn't One Right Way
to do it in Quixote. Given a dozen Quixote developers, you'll get a
dozen very different looking applications. You'll get them fast, and
they'll all be wonderful, I'm sure; but they won't necessarily bear
much resemblance to each other. This is in contrast to the "here's
what to use" philosophy of TurboGears, Django, etc. It's apples and
oranges.

> If you think that the community size is big enough. Then I would
> appreciate how you can convince a customer for your Quixote application
> compared to other (f.e. Zope, Cherrypy, ...)

Conceptually, CherryPy and Quixote seem relatively similar; Zope is an
entirely different animal. Quixote gives you a tremendous amount of
flexibility and freedom to choose the tools you need to solve a
problem, without including a whole host of unrelated stuff. I suppose
in a way Zope3 does the same thing, being interface-driven and all
that, but I imagine that the learning curve is much higher. Some
people get their jollies swimming in interface declarations and XML
configuration files; others like to get stuff done fast and improve
incrementally. Chacun a son gout; the world's a better place for
having alternatives.

Quixote will do its job and get out of your way, it won't tell you how
to write your templates, connect to your databases or deploy into your
production environment. Whether that's a good thing for you or for
your customer is an open question.

Just my two cents. I'm not an Official Quixote Cheerleader, and my
opinions are no one's but mine. :-)

Graham