Hello everyone, welcome to another one of my blogs.

In this blogpost, I will cover how git works, because.. why not. Git is a version control software, and it will save all the previous versions losslessly, so you can save all your code in a smart way. So, how does it work? Like so:

For each file, git tracks its hash as the files identifier, because it doesnt only cover the e. g. filename, but also the contents, name, etc. Then, for every new hash, it also saves the file contents, so it can retrieve them later.
When you use git commit, it creates hashes for each file, and checks if it already is in the 'database'. If now, it adds it, aswell as the hash. Its also good to note that git uses SHA1, which has prooven to be not secure, however git doesn't need the file hashes to be particularily secure, and the chance of 2 files conflicting is low enough to keep the compatibility for couple decades now.

Anyways once all the files are analysed, git simply updates its 'database' to have the proper file structure, and thats it! Now I am using the word database really losely here, but the whole word database is misused in like 50% cases anyways, so who cares.

You may be wondering, since this is quite a good system, why not use it for other things? And thats a good point. For example for paragraphs in document editors etc. But you sadly cannot use it everywhere, for example in filesystems. In theory you could, but to reach anywhere above satisfying the sata interface of 600mb/s with tiny files inside, you may need a hashing accelerator to download a game! And not gonna lie, that sounds very fun, installing a 30 000$ accelerator to download 80gigabytes worth of files.

Anyways that will be it for today, maybe I will even publish these eventually agin.