Idk
Sapling: A new source control system with Git-compatible client
321–330 of 543 posts
Re: Sapling: A new source control system with Git-compatible client
#322Nobody commented on the web interface yet which I think it's one of our coolest features: https://sapling-scm.com/docs/addons/isl
I'm sort of amazed that git and mercurial haven't built something like that yet. Makes me a little sad that Facebook created a new scm instead of expanding mercurial to include features like this.
Sapling is a fork of Mercurial. It isn't a completely new scm.
Re: Sapling: A new source control system with Git-compatible client
#323Its interesting how these threads about Git simultaneously have (a) People arguing git is fine, and shouldn't be simplified (b) People arguing about the right way to use git, and flame wars about best git workflows I mean most people simply see (b) and conclude "this is a huge hassle, I don't want to annoy some git-workflow-purist, I'm just going to walk on eggshells on this tool and hope I don't break anything" It's…
I remember when git was new, and the subversion crowd didn't jump on. Same discussion, different subjects. Git is/was awesome... but there is certainly room for improvement.
Subversion? You mean that unimpressive flash-in-the-pan CVS clone?
Re: Sapling: A new source control system with Git-compatible client
#324Not a big fan of FB as a company, but I think their open source work is pretty impressive. Various other large companies have the problem of giant monorepos that they constantly need to onboard new developers to, but I can't think of anyone other than FB who consistently released their solutions. Sure, most people are probably fine with Git once they learned it and if they only work with small to mid sized code bases…
Facebook has a lot of interesting open source projects, but they tend to abandon them. As far as oss goes, I think Google is the best. As long as you don't mind dealing with 3 different custom build systems within the same codebase, their projects usually have dedicated teams maintaining them. ...and yes, I realize it's weird to say this considering Google is known for abandoning things. Maybe it's just coincidence t…
What has FB abandoned? Cuz there is an entire website[1] for Google.
Re: Sapling: A new source control system with Git-compatible client
#325The interactive tool looks amazing. I do interactive rebases quite often and a drag-drop setup is wonderful However, I don't understand why I would want 1 PR per commit. I feel like that's a non-starter for me. Is the idea that no one should use branches - so there's only 3 points of interest: HEAD, main, and origin/main? And then is the idea that it's only 1 commit per feature to merge? So I would work on something,…
No, stacking is a (partial) workaround for Github "pull requests" being bad, by reimplementing the ordinary Git way to submit changes (one email per commit, reviewable inline. look at any patch thread at https://public-inbox.org/git/).
Doing this doesn't really make them good, but it makes them at least reviewable.
Re: Sapling: A new source control system with Git-compatible client
#326Earlier quoted context omitted.
Forget the CLI. VSCode implements a ton of git features as commands, which can be bound to any keybindings. For me this is way faster than CLI, as I don’t even need to leave my text editor - I have it set up chorded, so AltG followed by P,U,C,Y, will push (actually sync), pull, commit, undo, respectively. Two keystrokes beats any CLI interaction I’ve seen. (Disclaimer used to make VSCode)
Most people's objections to git ergonomics is not that the commands are slow to type. VS Code exposes the exact same operations on the underlying repository as the CLI, and it's those operations that critics say are hard to understand and cumbersome to use.
The parent said:
> This looks incredible. A simple command to uncommit or unamend makes you further realise what a disaster the Git CLI is.
I said that simple command already exists in VS Code. Yes it can be done via CLI, but not as simply as in VS Code. Not sure what your claim is.
Re: Sapling: A new source control system with Git-compatible client
#327Hi Hacker News! Author of the Sapling blog post here. I'm happy to answer any questions you might have.
Hopefully a dumb question that I missed an answer for in the docs. If I have an existing git repo (not hosted on github), is there a way to try using sapling with it? Or do I need to clone it from scratch?
My impression from the blog post is that I can use sapling and have everything "look" git-like from the remote repo's point of view.
Re: Sapling: A new source control system with Git-compatible client
#328In the argument of monorepo vs not, the usual argument goes like this: - It's too hard to scale for a large monorepo! - Google does it just fine! - But I don't have access to Google's tools! So kudos to Meta for both solving the problem and making it available to others. It will be interesting to see how useable it is outside of Meta. I know for example that while Netflix open sourced a lot of tools, most of them wer…
But they haven't done that yet. This is just the CLI, the centralized monorepo bits aren't yet available.
You could use Phabricator today.
Re: Sapling: A new source control system with Git-compatible client
#329Does it support commit signing? I spent a while reading the website and couldn't find anything suggesting it does. Lack of that is a showstopper for me (and frankly, should be a showstopper for anyone).
Please stop signing commits
Re: Sapling: A new source control system with Git-compatible client
#330Looks like the typical FB thing to do. Latch on to some popular tech like git and try to sell it as innovative or "better" gathering the fanboys. After a few years the marketing hype will blow over and we will either have lots of misinformed newbies, who got into dev work on FB products. Just like we have today lots of web devs able to throw together any react widget you want, but unable to gradp when simple server side templating in any web framework would have been sufficient. Hammer. Nail.
I for one will remain skeptical. If they release it as free software, we can talk. Probably real innovation will happen elsewhere though, without the FB flavour to chew on.