Sapling: A new source control system with Git-compatible client
engineering.fb.com
Sapling: A new source control system with Git-compatible client
1–10 of 543 posts
Re: Sapling: A new source control system with Git-compatible client
#2Originally started as an extension to Mercurial, but grew into its own SCM with a cross-platform virtual filesystem in C++ and a distributed server in Rust.
Re: Sapling: A new source control system with Git-compatible client
#3Re: Sapling: A new source control system with Git-compatible client
#4It’s hard to overstate how much better this workflow is UX-wise than the git(hub) default. I’m super excited to see it open sourced.
Re: Sapling: A new source control system with Git-compatible client
#5the number of projects that require the scaling factor of something like this is very small. git with lfs scales very well for most repositories. That said the actual flow of git is pretty raw. There are other pretty solid projects out there that support undo commands into git.
Stacked PRs are a blessing and a curse - still not convinced they are the correct way to build software as a team.
Re: Sapling: A new source control system with Git-compatible client
#6No post body was provided.
Re: Sapling: A new source control system with Git-compatible client
#7the number of projects that require the scaling factor of something like this is very small. git with lfs scales very well for most repositories. That said the actual flow of git is pretty raw. There are other pretty solid projects out there that support undo commands into git. Stacked PRs are a blessing and a curse - still not convinced they are the correct way to build software as a team.
Eh, it’s pretty hard to make a case that you don’t want stacked diff sometimes.
Obviously life is simpler if all your work is sufficiently non-intersecting that you can send separate diffs/PRs and e.g. rebase them separately, but if you have Big Feature X and you still want small, single thesis diffs, where else do you turn?
Re: Sapling: A new source control system with Git-compatible client
#8I’ve been using FB’s mercurial fork for years, wishing for all that time that I could have the joy of the fb-hg CLI while remaining compatible with github because that’s where 99+% of the code lives - from my brief experimentation, sapling appears to be that. I look forward to never using the git CLI again :D
Re: Sapling: A new source control system with Git-compatible client
#9This won’t go anywhere even if its 20% better than git. To replace git’s network effects, you need to be 10x better.
How I think that will happen is using CRDTs against an AST to remove most merge conflicts.
Re: Sapling: A new source control system with Git-compatible client
#10I’ve been using FB’s mercurial fork for years, wishing for all that time that I could have the joy of the fb-hg CLI while remaining compatible with github because that’s where 99+% of the code lives - from my brief experimentation, sapling appears to be that. I look forward to never using the git CLI again :D
I felt the same joy on reading the overview. Cleans up the git workflow so nicely.
...until I got to pull requests (Granted, that is github, not git). But it looks like you cannot generate a standard pull request with it.
https://sapling-scm.com/docs/git/intro#pull-requests
Haven’t tried it yet, looking forward to it.