The response to Sapling within the developer community has been a mixture of curiosity and cautious optimism. It's a tool that arrived with the promise of addressing the complexities of version control, particularly for those grappling with large monorepos. Yet, as with any new tool, it has been met with its share of skepticism.
Much of this post draws on feedback from this HackerNews thread on Sapling's press release.
Developers have noted Sapling's intent to simplify the version control process. The UI is recognized for its attempt to streamline workflows, and the Git integration is acknowledged for trying to offer a bridge between new and familiar workflows. However, developers have also been vocal about the learning curve and the potential limitations that come with oversimplification.
Critiques often center on the early stage of development for Sapling, pointing out features that are missing when compared directly to Git, such as hooks and certain community tools. Yet, there's also praise for Sapling's initiative to innovate within the space, with developers highlighting the potential benefits of a system designed for ease of use and scale.
Many developers express a wait-and-see attitude, intrigued by the possibilities Sapling presents but also mindful of the reliability and depth of Git that they’ve come to depend on. The balance between welcoming innovation and clinging to the tried-and-true tools of the trade is a common theme in discussions around Sapling.
Anticipation for future developments, such as the release of Sapling Server and Virtual Filesystem, is palpable in the developer community. There's a sense of eagerness to see how Sapling evolves and whether it can truly compete with or complement the established giants of source control.
Sapling has been a topic of discussion among developers, and various opinions have surfaced, offering a glimpse into the real-world application of the tool. Here are some direct quotes from developers that provide a spectrum of views on Sapling:
One developer expresses interest in the tool's potential to simplify their workflow, "I'm very keen to use Sapling if it's basically a polished interface to Git..." but also voices concerns about having to learn a different system.
Another developer, intrigued by Sapling's local cloning feature, says, "...I didn't even know you could do that in git. I always considered clone to mean 'download stuff from this location' but now it makes more sense..." which shows the appeal of Sapling’s approach to cloning and its learning curve.
Discussing Sapling's approach to commits, a developer mentions, "It facilitates the mental model for developers without actually removing workflows..." This reflects a recognition that while the workflows are different, they may not be unnecessarily complicated.
Internal feedback seems positive, "We think and many of our internal users agree that the UX alone is a worthwhile upgrade..." However, another developer counters, "I don't doubt the UX is better but internal users are a captive audience..." suggesting that the real test comes when users outside of Meta adopt Sapling.
One developer appreciates the diversity in source control solutions, "But I'm still happy Sapling is out there I might use it or learn from it if I ever run into the problems it solves..." indicating that while content with Git, they are open to exploring Sapling's offerings.
A Meta employee shares their experience, "As a Meta employee for almost 4 years...the sapling system works very well in practice in my experience..." and another adds, "I like sapling better than git. Who needs branches? Why stress about detached heads?" These comments suggest that those who have used Sapling extensively have found its features to be beneficial.
These quotes from the developer community highlight a range of perspectives on Sapling, from cautious interest to endorsement, and underscore the tool's potential impact on the developer experience.
Developers are watching Sapling with a critical but hopeful eye. The response underscores the tech community's desire for progress but also its commitment to functionality and robustness. As Sapling matures, its reception is likely to evolve, potentially reshaping the landscape of version control systems.