A git implementation in pure JavaScript

The node.js JavaScript surge reminds me a bit of the early days of Java, where everyone went to implement whatever existed in C/C++ for Java. Only that this time people stick a ".js" in the end instead of a "J" in the front.<p>If history has a lesson, most of this will not be wildly successful, because the js environment is not suitable for the task to be an actual practical solution.

OK, I was going to implement write support before posting it up here, but glad you guys like it.<p>There's tons more to do :)

I thought about doing an in-browser git implementation for enabling offline mode in a webapp. Doing things with git would make some really interesting sync scenarios possible. Looking at what was involved though, I think I'm glad I didn't go down this particular rabbit-hole.

FYI, it only does reading but it's still very impressive. I've tried out the demo and it just works against small repos. It's very slow against larger ones.

Yet more evidence of Atwood's Law:<p><i>Any application that can be written in JavaScript, will eventually be written in JavaScript.</i><p><a href="http://www.codinghorror.com/blog/2007/07/the-principle-of-least-power.html" rel="nofollow">http://www.codinghorror.com/blog/2007/07/the-principle-of-le...</a>

Awesome, when this can do writing (presumably with an in-memory store for now), I think there will be some really interesting in-browser version control uses.

what javascript testing library is it using?

why?