Live data from Hacker News

Sapling: A new source control system with Git-compatible client

engineering.fb.com

241–250 of 543 posts

Re: Sapling: A new source control system with Git-compatible client

#241
post #229

Nooooooooooo. Whatever is to come of my cute animations! [Think of the trains!]( https://github.com/mtoyoda/sl )

Yep, you'd think `sp` would be a better choice.

"sap" would be ideal, as it's also in keeping with the theme of using mildly offensive names.

Re: Sapling: A new source control system with Git-compatible client

#242
post #238

What exactly does “git compatible” mean? I may have missed it, but didn't see it skimming the post.

I’d like more detail on this too. I’m interpreting this to mean that anything you can do with git, you can do with sl, but I wonder what limitations exist for that. There have got to be some, somewhere along the way. Even just edge cases! Is it as simple as swapping ‘sl’ for ‘git’ in your terminal and workflow and nothing else changes? Surely not…

Re: Sapling: A new source control system with Git-compatible client

#243

I just cannot understand how a CTO approves this type of project. Imagine running a company and some engineer comes in and and says they want to develop a new source control system. I don't understand under what circumstances this is approved. Is it a pet project for a 10x engineer and it's allowed just to keep them on board? There are projects, like Apache Hadoop, that are open-sourced because they're an open-source…

I think projects like this happen at two extremes of company size. Small companies, where the team is a few engineers empowered to do whatever without having to justify to "adult supervision", and megacorps where there is actually a team, with engineers assigned, who's job is something super specific like "manage our source control"

Re: Sapling: A new source control system with Git-compatible client

#244

I just cannot understand how a CTO approves this type of project. Imagine running a company and some engineer comes in and and says they want to develop a new source control system. I don't understand under what circumstances this is approved. Is it a pet project for a 10x engineer and it's allowed just to keep them on board? There are projects, like Apache Hadoop, that are open-sourced because they're an open-source…

The simple reason is that Mercurial and git were way too slow for large repos, and FB wanted a monorepo for productivity reasons. It's cheaper to fund this project than reduce engineering productivity by even 1% at the scale of FB.

Google did exactly the same thing, but hasn't open-sourced their tools.

Projects to drive incremental productivity make not a lot of sense for small companies, but become immensely valuable at very large companies. A 1% improvement if you have an engineering staff of even just 10k is worth 100 engineers, and FB is much larger than 10k.

Re: Sapling: A new source control system with Git-compatible client

#246
post #24

Not 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…

React Native hasn't yet reached v1.0. Or several critical issues hasn't been addressed yet as of now.

Re: Sapling: A new source control system with Git-compatible client

#247
post #87

Thank god. I have been waiting ten years ( https://www.google.com/url?q=https://stevebennett.me/2012/02... ) for someone to develop a better CLI for git, someone with the scale and clout to do it well and gain mindshare. It's not that useful to learn a new workflow if no one you ever work with will be familiar with it. This looks incredible. A simple command to uncommit or unamend makes you further realise what a dis…

Check out jj, it's made by someone who works on Google's source control

https://github.com/martinvonz/jj

Re: Sapling: A new source control system with Git-compatible client

#249

I just cannot understand how a CTO approves this type of project. Imagine running a company and some engineer comes in and and says they want to develop a new source control system. I don't understand under what circumstances this is approved. Is it a pet project for a 10x engineer and it's allowed just to keep them on board? There are projects, like Apache Hadoop, that are open-sourced because they're an open-source…

[deleted]

Re: Sapling: A new source control system with Git-compatible client

#250

I just cannot understand how a CTO approves this type of project. Imagine running a company and some engineer comes in and and says they want to develop a new source control system. I don't understand under what circumstances this is approved. Is it a pet project for a 10x engineer and it's allowed just to keep them on board? There are projects, like Apache Hadoop, that are open-sourced because they're an open-source…

> Imagine running a company and some engineer comes in and and says they want to develop a new source control system. I don't understand under what circumstances this is approved.

Under the circumstance that no existing source control system can handle a monorepo as large as Google's or FB's. The custom source control system is not a hobby. It is vital to both companies.

Post reply on HN