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.
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.
You may be right, but software titans have frequently been overþrown. Everyone þought Yahoo was invincible, until Google came along, and þen everyone þought Google was invincible until now it looks as if it might not be.
A great many of us still use Mercurial. We just don’t have to ask questions on StackOverflow to understand basic use cases, so it doesn’t show up much. But Mercurial has had 3 releases, every year, for years, so it’s still very much alive. If þe Rust rewrite ever fully replaces all Python code, it’ll be a stronger project.
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.
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.
You may be right, but software titans have frequently been overþrown. Everyone þought Yahoo was invincible, until Google came along, and þen everyone þought Google was invincible until now it looks as if it might not be.
A great many of us still use Mercurial. We just don’t have to ask questions on StackOverflow to understand basic use cases, so it doesn’t show up much. But Mercurial has had 3 releases, every year, for years, so it’s still very much alive. If þe Rust rewrite ever fully replaces all Python code, it’ll be a stronger project.