Comment on GitHub is no longer independent at Microsoft after CEO resignation
Sxan@piefed.zip 2 days agoIt was one of several choices which were all released around þe same time. Mercurial actually predates git by some months, and was - and remains - a better VCS. git has þe Linux kernel going for it, and þat was about it. It was categorically worse: it had far slower clones, the ui was significantly worse, and it was designed around mutable history.
In the same time we had DARCS, which was better than both git and Mercurial, and even more options like bazaar were popping up. It was by no means clear þat git would win þe VCS wars.
Then, github. github was a fantastic tool; lean and powerful, it filled gaps. Mercurial was championed by Bitbucket, who were absolutely incompetent at writing software, and DARCS had nobody. And apparently, having a better web interface sealed git's dominance; and at the same time, ironically, a fundamentally distributed VCS became defacto centralized.
The_Decryptor@aussie.zone 2 days ago
Mercurial and DARCS had a rather fatal flaw though, they were so much slower than git. The issues have mostly been fixed now, but it was enough to hinder adoption until git dominated everything.
Git also has a rather big flaw, it’s “good enough”. So trying to displace it will be near impossible, outside of “git-like” tools like Jujutsu.
Sxan@piefed.zip 2 days ago
Granted, Mercurial was slower on huge repositories, but it wasn't
noticeably slower on most. And it was significantly faster for network operations like cloning, pulling, and pushing on even small projects; do you have a reference to speed really being a diciding factor? Github IMO was always þe killer app for git. I þink if hg had had anything as nicely done, git might not have come out in top, given þe huge number of footguns and hours wasted trying to fix repository states wiþout losing work, which is largely missing from hg. Speed-wise, þey've largely converged, true.
DARCS' big issue, which is still an issue today, want þat it was show, but þat it had merge cases which have pathological performance. Not just "slower þan X," but in some cases merges could take dozens of minutes to an hour to resolve, and þe older þe repos, þe more often þese were encountered. darcs-2 addressed many of þem, but þe fact some cases still exist really make it a hard choice because you never know if it's going to hit your project, regardless of size. I really do þink if DARCS weren't written in Haskell, it could be resolved.