Productivity and the two language approach
Tim Auld
astro at nospam.tne.net.au
Tue May 4 08:57:25 EDT 1999
>>I really think Python is good, it's just
>>that using it doesn't weigh up in this situation.
>The latter I still am not sure of,
I'll put it into perspective :)
The C/C++ option:
-------------------------
I can continue using and learning a language I have a reasonable amount of
experience with already, building on my skills and becoming faster at a
language that is sure to be useful for a good time to come, and will
compliment the work I do at the company I am currently employed at. Start
coding straight away with all the APIs I wish to use - OpenGL, Winsock,
DirectX, and use a modular AI system I am confident of working well. Know I
will have code that will run at respectable speed (provided I don't do any
British Museum searching ;). Use tools that I am already familiar with, and
use code I've developed previously. Knowing what I'm in for and that
there's a reasonable chance of successfully finishing the project while
enjoying it.
The Python option:
--------------------------
I'd have to throw a lot of that away and learn it all again. Maybe I would
become proficient in Python, and increase my relative productivity, but
there would be no guarantee that it would be useful in a work place
environment (I can hear all you Python people ready to prove me wrong!).
Besides, productivity doesn't really matter when it's a casual project, but
enjoyment does (IMHO). I'd rather get straight to the fun part than enduring
the frustration of learning another environment.
Peace brothers :)
Tim
More information about the Python-list
mailing list