MOmodinfo·Oct 17, 2026Submission
Sl – A Scalable, User-Friendly Source Control System
1 points · Open discussionmeta
sapling
Rust2017–2026
meta / sapling
sapling
A Scalable, User-Friendly Source Control System.
59Distinct people
67Mentions
0Explicit recommenders
7.3KGitHub stars
What to know before exploring
What it is
A Scalable, User-Friendly Source Control System.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- jj-vcs/jj · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year67 dated mentions
Observed mentions: 2017-02-08 21:58:08 UTC to 2026-10-17 13:22:50 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 18 | 2 | 16 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 13 | 4 | 9 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 9 | 1 | 8 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 8 | 0 | 8 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 5 | 1 | 4 |
What Hacker News says
67 sourcesRelated, I've always wanted to see someone other than Meta run EdenFS, to hear more reports of what it's like. Feels like there's massive overlap. [Edit: I've chatted with Astra Pro some on this too now, https://chatgpt.com/share/6ace7be6-68f8-83ea-ad68-0f9d144483...
]. https://github.com/facebook/sapling/blob/main/eden/fs/docs/O...
It's designed for container running, but ArtifactFS has some similarity in principle to me. The on-demand materialization. Quote: ArtifactFS is a Git-backed filesystem daemon (FUSE driver) in Go that mounts repositories as normal working trees while avoiding eager blob downloads. https://github.com/cloudflare/artifact-fs
I threw together my own jujutsu powered FUSE subtree project just the other night. This was basically one-shotted, just to see how it does it, to learn more, not really intended for use. But
Read the rest
obvious overlap. https://github.com/rektide/jj-workfuse
https://github.com/facebook/sapling Anyone outside of FB using it?
In Ask HN: Alternatives to GitHubIt annoys me greatly that the megacorps have all these fancy devtools that we plebs have no hope of touching. One example being Metas Sapling, which afaik is their way of making git-compatible vcs perform decently well at their scale. Sure it is nominally open-source, but the readme has enough notes like "Not yet supported publicly, OSS is buildable for unsupported experimentation." to dissuade any casual users. And afaik the others have their own things, mostly even less public.
https://github.com/facebook/sapling
In High Performance GitI have used savevers.vim for many years as a way to recover old versions of files.
https://www.vim.org/scripts/script.php?script_id=89
It is comparatively unsophisticated, but I need it so infrequently that it has been good enough.
I do like the idea of maintaining a complete snapshot of all history.
This is a good application for virtual filesystems. The virtual fs would capture every write in order to maintain a complete edit history. As I understand it, Google's CitC system and Meta's EdenFS work this way.
https://cacm.acm.org/research/why-google-stores-billions-of-...
https://github.com/facebook/sapling/blob/main/eden/fs/docs/O...
In Show HN: Unfucked - version all changes (by any tool) - local-first/source availThe headline times are a bit ridiculous. Are they trying to turn https://github.com/facebook/sapling/blob/main/eden/fs/docs/O... or some git fuse thing into a product?
In SourceFS: A 2h+ Android build becomes a 15m task with a virtual filesystemYou might be interested in how this problem was solved by our team at Meta, in EdenFS (https://github.com/facebook/sapling/blob/main/eden/fs/docs/O...) and Watchman: https://github.com/facebook/watchman.
What you're describing is reasonably similar to EdenFS, except EdenFS runs in userspace.
Watchman layers a consistent view of file metadata on top of inotify (etc), as well as providing stateless queries on top of EdenFS. It acts as a unified interface over regular filesystems as well as Eden that provides file lstat info and hashes over a Unix domain socket.
Back in the day, Watchman sped up status queries by over 5x for a repo with hundreds of thousands of files: https://engineering.fb.com/2014/01/07/core-infra/scaling-mer... I worked directly on this and co-wrote this blog post.
In truth, getting these two components working to the sta
Read the rest
ndard expected by developers was a very difficult systems problem with a ton of event ordering and cache invalidation concerns. (With EdenFS, in particular, I believe there was machine learning involved to detect prefetch patterns.) For smaller repos, it is much simpler to do linear scans. Since it is really fast on modern hardware anyway, it is also the right thing to do, following the maxim of doing the simplest thing that works.
Is it still used at Facebook? I know they did in the past, but reading up a bit on the background on all of this I found https://github.com/facebook/sapling, and it seems that's what they're using now?
In Ask HN: Why Did Mercurial Die?:(How does this compare to sapling? https://github.com/facebook/sapling
In Jujutsu for busy devsIs it still used there? I know they did in the past, but reading up a bit on the background on all of this I found https://github.com/facebook/sapling, and it seems that's what they're using now?
In Mozilla Firefox – Official GitHub repoSapling is actively developed, not "dead after 3 months": https://github.com/facebook/sapling/commits/main/
Have not tried building Buck2 (no personal use for it), but its also actively developed: https://github.com/facebook/buck2/commits/main/
In Pyrefly - A faster Python type checker written in Rusthttps://github.com/facebook/sapling/tree/main/eden
I'm still unsure if a complete, viable eden solution was released with all of its necessary components.
In The next generation of Bazel buildsHow does it compare against Facebook's Sapling? https://github.com/facebook/sapling
In jj: a Git-compatible VCS that is both simple and powerfulMeta open-sourced their complete stack: https://github.com/facebook/sapling
Microsoft released Scalar (https://github.com/microsoft/scalar) although it's not a complete stack yet but it is already planning on releasing the backend components eventually.
Have you tried Sapling? It has EdenFS baked in so it'll only materialize the files you touch and operations are fast because it has a filesystem watcher for activity so it doesn't need to do a lot of work to maintain a view of what has been invalidated.
In Monorepo – Our ExperienceLarge checkouts is a solved problem now https://github.com/facebook/sapling/blob/main/eden/fs/docs/O...
In Bento: Jupyter Notebooks at MetaShowing the 15 most recent of 67 sources. Enable JavaScript to search and browse every indexed mention.