> Il 31/07/2020 17:55 Pierre-Yves David <pierre-yves.da...@ens-lyon.org> ha > scritto: > > I got int touch with the OpenJDK people one and half year ago. [...]
Very active move on your part. Kudos. > Moving to a modern Mercurial version, using sparse revlog for storage > and recomputing delta gave a massive boost to storage size and clone > performance. At least this reassures that performance-wise mercurial has not fallen behind so much. The tests performed by Josef and Joerg confirm that a performance disadvantage exists indeed, but it's not massive. > a good share was also lack of interrest in > actually improves their Mercurial situation. The crave to move to Github > for community reason was strong. I can understand wanting to benefit of the Github network effect, and do not want to focus on it here. What concerns me the most are two things: 1. scripta manent: when in some years people will google for "mercurial performance" they will stumble upon JDK considerations, and take them form granted. What will remain in a potential user's head is "mercurial is slow, go for git. JDK guys have done the same". There is no other written material counterweighting these moves (except for very interesting blog entries by Gregory Szorc, possibly), and so the collective mindset slowly slips away. 2. (consequence of 1) no mindset that another valid SCM exists: SCM == GitHub, because - obviously - git == "hosted service with integrated issue tracker, CI and whatnot", right? I am wondering if the countermeasures to this have to be only technical. I see this more as a communication disadvantage compared to the git ecosystem. _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
