GitSoft
The obvious one!
In all the furore around the acquisition of GitHub by Microsoft, no one has asked the obvious question: what should the service be called after its Redmondisation? At Vulture Central, we live in constant fear of mixing up GitLab and GitHub. Two letters are all that stand between an amusingly snarky story and a grovelling …
That isn’t the microsoft way; the first thing it needs is to divide the exact same thing into multiple tiers at different prices.
1. Enterprise edition git: eegit
2. Internet developer git: idgit
3.Mobile app git: magit
4. Federated k8s git: fkgit
And to help guide you to the right git for you: gippy, your git assistant.
OldGit—includes a plethora of appropriate mental images for UK readers, including imminent obsolescence, and correctly implies that all sentient users not yet victimised by Microsoft's "ecosystem"*¹ will be heading for something younger, better and less likely to become toxic.
*¹ "Ecosystem": Trap floored with poisoned punji sticks—refers to commercial practice of attempting to entrap paying customers via contrived dependence, usually on false and superfluous grounds, thereafter to squeeze their wallets until they die.