On Mon, May 16, 2011 at 8:33 PM, Jim O'Flaherty, Jr. < [email protected]> wrote:
> Petr, > > I would love to see a fully HTTP protocol based JSON server based using > asynchronous messaging. Contrary to some of the "I love to parse characters > and want as efficient as I possibly can down to doing bit twiddling > encoding/decoding on input/output even if it is no where NEAR the bottleneck > damn the humans and their ridiculous need to have things be readable", > I think you are confusing GTP with the horrible GMP protocol that came before it, that thing that actually did involve binary protocols, bit twiddling and a cable to connect to GTP engines. But your comment shows that you are completely ignorant about what GTP is. Take a look at the GTP document and you will see that it was specifically designed to be all the things you are ranting against. I think if you look at this protocol you will be very embarrassed by your silly comments above. I'm all in favor of improving or even changing to something better, but there has to be a strong need as well as an actual improvement for it to succeed and even then you have to fight inertia. This proposal does not satisfy neither of these fundamental things. If you want to build a local gogui like application, then I believe it's not correct to put more burden on the engine, Darren Cook has the right idea here. Let the go engine play go. Have some other piece (that people can share) do the heavy lifting with an adapter script. In fact, take a good look at gogui - each piece does only 1 thing and does it well with real simplicity. It's a work of art in many ways. Don
_______________________________________________ Computer-go mailing list [email protected] http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
