Python evangelists unite!

[Peter Milliken]

Agreed Jim :-), there are many shades of grey in between. Note that I have
never said that you *can't* do it in Python - just that I believe there are
better languages for larger programs i.e. the cost of production would be
less in some languages than if you did it in Python - this must also be
tempered with exactly what you are coding i.e. Python is very, very good at
certain things, therefore if your program would benefit from those features
of the language then by all means - there are rarely any absolutes in this
world :-).

Just like you can produce large programs in C++ (but I wouldn't personally
:-)) - just out of curiousity, why was the C++ version of the product
replaced by a Jython version? Too difficult/expensive to update to the new
requirements?

Any ideas of what the maintenance costs of the C++ version were in
comparison to any other language? Was the Jython version cheaper, more
expensive or the same in terms of productions costs as the C++ version? What
were the problems encountered by the various teams using Jython? It has
always interested me what the selection process is in choosing a language
for a project - do you know how and why Jython was chosen? Was it because of
popular aclaim or was some formal comparision of various languages
performed? If there was some formal selection process, what languages were
considered? What features of Jython caused it to be selected? i.e. what
features where missing in the other languages under consideration.

Peter

<James_Althoff at i2.com> wrote in message
news:mailman.1007425027.30019.python-list at python.org...
>
> Peter Milliken wrote:
> >Obviously you haven't worked at the architectural
> >level of any *large* projects (10's or even 100's of programmers)
> otherwise
> >you would never make the statements you do. Ignorance is bliss I guess
:-)
>
> But since all things are not simply "black or white" you might want to
keep
> in the back of your mind the fact that our company has written a
successful
> commercial product that comprises several hundreds of thousands of lines
of
> Jython code written by several dozen programmers working in multiple
> locations throughout the world and has been in production use for over a
> year and is expected to be supported for many years to come (the C++
> product that it replaced has been supported in production use for over
> seven years and counting).
>
> Jim
>
>
>