Sapling
A Git-compatible version control client open-sourced by Meta, designed to handle extremely large monorepos and histories of billions of files, with targeted optimizations for managing large-scale binary assets.
Timeline (last 90 days)
Sapling was developed by Meta, originally serving its hyperscale monorepo, and emphasizes scalability and native support for stacked diffs.
Neither Jujutsu nor Sapling abandoned Git's object model; instead they rebuilt the interaction layer on top of it.
Systems such as Perforce and Sapling have made targeted optimizations for managing large-scale binary assets.
Meta's open-sourced Sapling is a Git-compatible client rebuilt to handle ultra-large-scale monorepos and histories of billions of files.
New-generation version control tools such as Jujutsu and Sapling tend to redesign the underlying data model.
All Facts (5)
Sapling was developed by Meta, originally serving its hyperscale monorepo, and emphasizes scalability and native support for stacked diffs.
50%UnverifiedNeither Jujutsu nor Sapling abandoned Git's object model; instead they rebuilt the interaction layer on top of it.
50%UnverifiedSystems such as Perforce and Sapling have made targeted optimizations for managing large-scale binary assets.
50%UnverifiedMeta's open-sourced Sapling is a Git-compatible client rebuilt to handle ultra-large-scale monorepos and histories of billions of files.
50%UnverifiedNew-generation version control tools such as Jujutsu and Sapling tend to redesign the underlying data model.
50%