Roy Smith wrote: > I'm working on a product which for a long time has had a Perl binding for > our remote access API. A while ago, I wrote a Python binding on my own, > chatted it up a bit internally, and recently had a (large) customer enquire > about getting access to it. > > I asked for permission to distribute the Python binding, and after a few > weeks of winding its way through the corporate bureaucracy I got an email > from a product manager who wants to meet with me to "understand the market > demand for Python API before we commercialize it". > > Can anybody suggest some good material I can give to him which will help > explain what Python is and why it's a good thing, in a way that a > marketing/product management person will understand?
There isn't an immediate economical benefit, but a technician has to care for the "state of the art". It is both a net-effect regarding technologies and developers but also something more vague, which is a little harder to get: a product has to have a certain appeal. Perl might have been a good decision 10 years ago but appears a bit shaddy these days where better designed languages exist with equal power and far more clean APIs. -- http://mail.python.org/mailman/listinfo/python-list
