[computer-go] language choices

[Chrilly]

>A note: we're working on converting Orego back from C++ to Java, and
> we're getting 5,000 (totally random at this point) simulated games  per 
> second. We'll probably continue in this direction.
>
> Peter Drake
> Assistant Professor of Computer Science
> Lewis & Clark College
> http://www.lclark.edu/~drake/
>
Probably the most important feature of any programm is the Bugs/sec. rate. 
One method to find bugs is to have 2 independent versions and to compare the 
results. This is common practice in hardware design where one has e.g. a C 
version/simulator and a VHDL/Verilog design. Or everything is in VHDL but 
its programmed at different abstract levels. I does not help against 
conceptual bugs, but one catches at leas the "stupid" bugs. I have found 
this technique very usefull in Hydra.
I think one should to the same in software-development too. But it is 
usually only done in very mission-critical software. But in your case you 
have already a Java and a C++ version. This is a big chance. I would develop 
both versions further in parallel.

Chrilly