> The general rule (in my opinion) is that playing strength will require a huge > amount of "power" because that's what A.I. is. This in no way implies that > it should not be "efficient" or that it should foolishly squander resources > (as an internal combustion engine does.) Instead it should be as efficient > as possible specifically so that it can do more work. And your not going to > squeeze much water out of a rock. You're not going to get a free ride. You > are not going to produce a strong program that doesn't do an enormous amount > of work. Naturally, you want to do that work as efficiently as possible. > The reason you want the work to be as efficient as possible is so that you > can do even more work, not because you are seeking the holy grail of a > program that plays like a master with a few lines of clever code and a > constant time algorithm.
Don, I think you're very much arguing against a straw man at this point. _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
