Gitlet: Git implemented in JavaScript

I wrote a short post about how and why I made Gitlet: <a href="http://maryrosecook.com/blog/post/introducing-gitlet" rel="nofollow">http:&#x2F;&#x2F;maryrosecook.com&#x2F;blog&#x2F;post&#x2F;introducing-gitlet</a>

I really liked your &quot;Git in 600 words.[1]&quot; I think it will help clear up some confusion for some of my VCS wary colleagues.<p>1. <a href="http://maryrosecook.com/blog/post/git-in-six-hundred-words" rel="nofollow">http:&#x2F;&#x2F;maryrosecook.com&#x2F;blog&#x2F;post&#x2F;git-in-six-hundred-words</a>

See also: <a href="https://github.com/creationix/js-git" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;creationix&#x2F;js-git</a><p>Kickstarter: <a href="https://www.kickstarter.com/projects/creationix/js-git" rel="nofollow">https:&#x2F;&#x2F;www.kickstarter.com&#x2F;projects&#x2F;creationix&#x2F;js-git</a>

I&#x27;ve asked GitHub to enable CORS for their https git endpoints, and I&#x27;m not the first. Email them at support@github.com if you can think of some cool stuff to do with that enabled.

It would be interesting to see this baked into a browser-based text editor. Make it fully client side and you can potentially save the git history in localstorage and use it as an offline web app. I wonder if there are any git servers that support websockets...

This is a collossal effort and a huge community service. Thank you for being so thorough in documenting your work. Even if others don&#x27;t directly use your code, you have given the world a great template to understand and implement git!

Some might also find js-git interesting: <a href="https://github.com/creationix/js-git" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;creationix&#x2F;js-git</a>

OT: I love the typography on your site, especially the little touches like the decenders overlapping link underlines.<p>edit: after some research turns out the link underline styling is a Safari thing. My point stands, though, the typography is wonderful.

&gt; Sometimes, I can only understand something by implementing it. So, I wrote Gitlet, my own version of Git. I pored over tutorials. I read articles about internals. I tried to understand how API commands work by reading the docs, then gave up and ran hundreds of experiments on repositories and rummaged throught the .git directory to figure out the results.<p>When the source itself is available, why not just read the code? I understand using articles and documentation to get the high to mid level view, but why not go to the real source of truth if it&#x27;s available?

A related way to learn is from git&#x27;s initial source, which was quite small. <a href="https://news.ycombinator.com/item?id=8650483" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=8650483</a><p>Warning: the file format has changed slightly.

Superb effort.

What are the expected use cases?

how are files handled ?

Why JavaScript?

This is the most extreme example of Atwood&#x27;s law that I&#x27;ve seen so far of.<p>Any volunteers for making an operating system kernel? Or has that been done already?

git is a tool that have to be introduced to as many as possible, even non-developers. In essence git is a fundamental part of the future global world collaboration. One can&#x27;t overestimate the gits value.