In article <[EMAIL PROTECTED]>, Paul Rubin <http://[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] writes: > > Where would you stop? At the boundaries of your particular application > > interests? > > If the Pythonistas are serious > about such a claim, competitive analysis says they should be willing > to look at what language L does to support application XYZ (example: > PHP includes database connectivity), make a checklist of L's features, > and see to it that Python achieves (at least) parity in those areas. Well, digging into this, php includes database connectivity if compiled against the database client libraries. So it's not as if you can just download php and have it work against the database you want. I also don't think that python as a general-purpose programming language is in direct competition to web frameworks like PHP and ColdFusion. Perhaps the right answer is to say that PHP is a better solution for people wanting a web templating framework with embedded scripting, while Python is a better solution for people who want a general scripting/application language with broad support for specific applications via add-on modules. But then again, I'm one of those heterodox people who argue that one should fit the tool to the problem. Common Lisp, bash, awk, sed and R are other great languages for different domains. -- http://mail.python.org/mailman/listinfo/python-list
