On Wed, Nov 21, 2007 at 12:07:03PM -0500, Don Dailey wrote: > My advice when this question comes up (which language for go programmer) > is to first ask, what do you hope to achieve? If you want to build a > high performance go program, anything other than C or assembler is like > tying your hand behind your back. If you do this only as a hobby and > have no aspirations (just for fun and pleasure) then by all means, you > will be much happier in a high level language.
Interesting approach. I like C myself, so even as an amateur just dabbling in the field, I have used it, and will do so again. But of course teh choice is never so black and white. If I had unlimited amount of time (or some student labour available ;-), I would make a good C library available from higher-level languages, so that the parts that matter could be fat and efficient C, and those that don't matter, or where lots of experimentation is useful, could be done in (say) python. There just isn't much point in optimizing much out of the 'list_commands' routine of the gtp interpreter, it is used at msot once per game, and communicating teh result over a network is going to be much slower than what ever is done to find the commands... - Heikki who does not plan to do much more in the language war... -- Heikki Levanto "In Murphy We Turst" heikki (at) lsd (dot) dk _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
