wasm-demo/demo/ermis-f/python_m/cur/1782

75 lines
3.5 KiB
Plaintext

From: fatjim at home.com (Jim Meier)
Date: Wed, 05 May 1999 17:01:32 GMT
Subject: Productivity and the two language approach
References: <newscache$bu0saf$a8n$1@news.tne.net.au> <7g94lp$mdu$1@news.worldonline.nl> <newscache$ck80bf$rc4$1@news.tne.net.au> <925677195.13550.0.rover.c3ade4b2@news.demon.nl> <newscache$bvp5bf$ri$1@news.tne.net.au> <925758153.6563.0.muttley.c3ade4b2@news.demon.nl> <newscache$lbl7bf$12p$1@news.tne.net.au>
Message-ID: <37307A6E.6502B8A3@home.com>
Content-Length: 3061
X-UID: 1782
Tim Auld wrote:
> 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.
But what happens when you want to script or extend your game? I'm working on
something (very, very vaguely) warcraft-like, and I'm letting everything be
extensible in python, as well as the entire story engine (other than the trigger
events themselves.) This means that me and the other guy fiddling with this can
make new behaviors and storylines without much fuss. Plus, with a good design,
you can allow your users to do things like define their own behaviors for
NPCs/units, generate graphs/reports, customize user interfaces, etc, etc,
etc... My point is that this fits like a glove your desire for a "modular AI
system I am confident of working well." As for tools you are alread familiar
with, go ahead and keep using them. The python stuff doesn't need any special
tools, as far as I've seen!
> 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.
(I'll leave it to the c.l.p regulars to get into the workplace part, I wouldn't
know - just a weekend hack{er})
You're right - productivity doesn't matter, and enjoyment does. Which is why
I'd encourage you to learn a new language. In fact, learn many new languages.
Actually, learn as much of everything as possible. That's what I've always found
enjoyable! :)
Seriously, Python takes all of ten minutes to begin coding in, all of an hour to
link into your C code (can't comment on c++, anyone else?), and c.l.p,
www.python.org and other resources from there will help you along with the
rest-- if you regulary read/write/breathe large C++ programs, absorbing this
material would be like pausing from sucking on a firehose to have a sip from a
dixie cup. (You can quote that if you're not embarassed about dixie cups. :)
>
> Peace brothers :)
>
> Tim
The perfect interjection in a language war!
-Jim.