3 ms·
The network effects associated with hosting code in a public source repository are just too great. If you want your code to be seen, used, trusted, you put it o
by mbreese 3y ago
The network effects associated with hosting code in a public source repository are just too great. If you want your code to be seen, used, trusted, you put it on one of the primary code repositories. At one point, this was sourceforge. For a while bitbucket had a good share. Then came GitHub.
There are also always a few secondary repositories that share the same tooling, but still have less traction (like GitLab). But the network effects of GitHub are hard to ignore.
But, like was said in a previous comment, it least it is easy to move Git repositories from one host to another. So when there is an inevitable successor to GitHub, we’ll all be able to migrate to the next hotness easier.
(That’s assuming that the next hotness supports Git. Prior shifts followed from changing underlying technologies… CVS -> SVN or Hg -> Git)