✳flâneur — a map of the web's best reading

Sapling: A new source control system with Git-compatible client | Hacker News

news.ycombinator.com · 37,155 words · saved by 1 readers

Facebook used to be involved with the Mercurial community, but it was difficult to work with them. They always wanted to do things their way, had their own intentions, and started to demand that the Mercurial project work the way that Facebook wanted. For example, they demanded that we start using Phabricator and started slowly removing sequential revisions from Mercurial in favour of always using node hashes everywhere, arguing that for their gigantic repos, sequential revisions were so big as to be useless. Eventually the disagreements were too great, and Facebook just stopped publicly talking about Mercurial. I figured they would emerge a few years later with their fork of it. They love doing this. HipHop VM for PHP, Apache Hive, MyRock; these are examples of Facebook forking off their development in private and then later emerging with some thing they built on top of it. The Mercurial project is surprisingly still chugging along, and there are still those of us who actually use Mer

Sapling: A new source control system with Git-compatible client | Hacker News Hacker News new | past | comments | ask | show | jobs | submit login Sapling: A new source control system with Git-compatible client ( fb.com ) 926 points by bolinfest on Nov 15, 2022 | hide | past | favorite | 525 comments jordigh on Nov 15, 2022 | next [–] Ah, there it is. I was wondering when this would happen. Facebook used to be involved with the Mercurial community, but it was difficult to work with them. They always wanted to do things their way, had their own intentions, and started to demand that the Mercuri

Explore this link on the map →

related reading