undefined | Better HN

0 pointsmojombo17y ago0 comments

It's not about that at all. I'm more familiar with Erlang than C, and the git source is a twisty jungle of advanced C code. I could have patched git-daemon, but to have a project that I can easily understand, maintain, and improve, I chose to write my own in Erlang. My tests show the Erlang and C git servers to be very similar in performance, so that's not a concern. And I can guarantee that egitd has far fewer lines of code!

I don't choose languages because they're cool or trendy. I choose them because they make it easier to Get Things Done. And for a startup, that's an unmistakable benefit.

0 comments

3 comments · 1 top-level

jrockway17y ago· 2 in thread

But now every time upstream makes a change, you have to reimplement it. And the users of the C daemon don't get your improvements.

Obviously you can do things your way, and you'll probably make money doing so... but it's still antisocial.

mojomboOP17y ago

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.

jrockway17y ago

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.

1 more reply

j / k navigate · click thread line to collapse