> The biggest issue here > is, of course, that the API will be changing, and changing in ways > that means that non-ruby developers won't be able to easily draw > parallels between their code and the ruby code. I view this as a > necessary sacrifice. Why is it necessary to break parallels so completely in order to make the API more Rubyish? We've had some changes suggested to the Python API to, for example, use named parameters and callables (instead of factories), but the basic structure of the library (and the interfaces) would remain the same.
> Are there any objections, suggestions, or questions here? I would suggest that you sync up early with Kevin Clark, the de facto owner of the current Ruby mapping. > Is there a git repository somewhere? There is an unofficial repo at <git://thrift-git.thruhere.net/thrift.git>. A lot of non-committers have been using it to develop and share experimental branches. I can give you an account so you can push branches if you send me your ssh public key. If you prefer github, it is mirrored at <http://github.com/dreiss/thrift/tree/master>, but I've been encouraging developers to also push their changes to thruhere so everything will be in one place. --David
