On Thu, Nov 15, 2007 at 04:41:19AM -0800, steve uurtamo wrote:
> the more i think about it, the more i love whatever language
> i'm using for whatever project i'm working on. some projects
> would be (or are) horrifying to try to implement in some languages
> [the matlab->C example springs to mind], so, since learning
> new languages isn't a gigantic burden, the only relevance is
> the intended application, i suppose. which is a very cumbersome
> way of repeating (reinforcing?) what other people have already said.
This also applies _inside_ the domain of Go, I guess. C-ish language
might be one of the natural choices if you are writing a Monte Carlo
style engine and need to have a blinding fast board library. But if you
are approaching the problem completely differently (say, heavy pattern
matching and complicated computations - but few iterations), some other
language might be quite more appropriate at least for the proof of
concept.
(Yes, you can write the board library in C and then build on that in
some other language. But in case of programs where the Monte Carlo or
something alike is at the core, it is likely the bulk of the code
anyway, and the part you will be debugging the most. Would the
additional headaches and overhead of mixing two languages pay off?)
--
Petr "Pasky" Baudis
We don't know who it was that discovered water, but we're pretty sure
that it wasn't a fish. -- Marshall McLuhan
_______________________________________________
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/
