Changes to the git protocol happen at a glacial pace. Keeping up with them will not be a problem. The only users of the C daemon that would benefit from egitd are our competitors. We've open sourced our Ruby git library since that has benefit to the community as a whole. I'd hardly call our decision to write an Erlang git server antisocial. As far as I can tell, it's not hurting anyone.

I didn't realize you weren't releasing egitd. If you're keeping it to yourself, it doesn't really matter what it does or what language it's written in.

Surely it matters insofar as people find it interesting to hear about, even if they might prefer to actually see the code.

Here's a piece of it that we did opensource. An Erlang pipe implementation. It acts as a FIFO for binaries.

http://github.com/mojombo/erlang_pipe/tree/master/pipe.erl

The performance ends up being quite good.

spaceship?

The comparison operator that returns -1, 0, or 1 depending on how the operands compare is often represented as <=> and commonly referred to as the "spaceship operator" because it looks like a flying saucer viewed from the side.

http://en.wikipedia.org/wiki/Spaceship_operator

Huh. I never heard it called that before.

My background is in math so I always though of it in terms of the sign function: http://en.wikipedia.org/wiki/Sign_function

spaceship(x,y) = sign(x-y), for numbers, anyhow.

FWIW, Larry Wall calls it the Spaceship Operator in "Programming Perl".