Git, if you are unfamiliar with it, is a software source control program, allowing you to check code (and other things; I’ve used it for documentation) in and out of a repository, which can be either local or remote.
GitHub is (for now) the most popular remote repository for Git. You can either put all your code in a public repository for free, or in a private repository for a modest per-user fee. GitHub makes its money off bells and whistles for private repositories.
Now comes word that GitHub’s “Social Impact Team” has decided “We don’t want any of those stinking white people here.” “It is very hard to even interview people who are ‘white’ which makes things challenging.”
Git and GitHub got to be where they are today because they’re both free-ish, but also because they’re deeply beloved of open source programmers not deterred by the steep learning curve of Git’s command-line-fu. But open source programmers, in addition to being distinctly pale of hue on average, tend to hate Social Justice Warrior types, if the comments on the SJW threads the “new” Slashdot keeps trying to cram down their reader’s throats on a regular basis is any indication.
Since Git (the program) isn’t limited to any particular repository, it’s fairly easy (remembering, always, that everything about Git falls into two general categories: trivial (because you’ve memorized and mastered the syntax) and impossible (because you haven’t)) to move your existing code to a new repository. And there are plenty of GitHub competitors, including a new one from Google.
No wonder GitHub is suffering an exodus of talent…
(Hat tip: Moe Lane.)