In the internet today almost everything gets cached. Every website you visit uses some caches. Either it is only a webserver filecache or one of the big players on market like cloudflare, fastly, keycdn, acamai or any other. In these cache systems static files can be stored for very long periods of time before it ends up expiring. But what happenes if you make any change, since the cached version of the file is stored in your visitors' browsers, they may be unable to see the changes made.

Cache busting solves the browser caching issue by using a unique file ...

I like having stuff high available. Everybody who works in IT knows it: Everything can fail and it most likely fails when you really need it as written in Murphy's law: "Anything that can go wrong will go wrong". Therefore I decided to cluster my UniFi Controller today. For sure it does not need to run on a server and can be started locally for configuration. But I like to have some nice stats and graphs which are also provided by the Controller and therefore it needs to be up and running constantly.

It can happen that you add some big files to Git (binaries, documents, images, ...) or some "private" files which should not be in git. Removing it from your filesystem with a single commit will just remove the file in the working tree, but Git does not fully delete a file when removing it via commit. Maybe you want to restore it. That's why Git keeps it in his history.