@andrewnez I miss subversion.

@andrewnez Yeah it does. unsurprising because git was created as a way to replace svn that could accommodate offline work. If you remove the offline requirement, it should be natural for the result to shift back to what svn was.

@andrewnez this sound an awful lot like something that is utterly broken and full of problems and barely works, but as we do not have to see it just their "ideas", then they get all the positive with none of the risk

@andrewnez They can claim it is such good quality and so performant and have so much test and defense because noone can attack it

@andrewnez Also they claim so many changes per minute that even if they regularly mangled and fucked up the merge, noone would know because there is no truth to compare it to.

It is the perfect "can't fail" project, because the outcome is such a mess that you can never know if the system did its job well or not.

We don’t expect this rate of growth to slow down anytime soon; the latent demand for merging code is practically infinite, and every bottleneck we remove immediately leads to a further increase in the amount of code we produce.

@andrewnez I was just thinking that...

@andrewnez What it sounds like is kinda irrelevant.

What the point of keeping a version control history of what must become layers of garbage, is what I am wondering.

There is no way they can quality check that amount of code. Are they rewriting the software from scratch each time and keeping a history of the previous version? how much nonsense code that never does anything is put in there?

I guess they feel these numbers they toss out should impress people, but if your fancy code-for-you system creates that much noise, it's everything else than impressive...

@andrewnez I wonder what's the case for monorepos. It feels quite a lot could have been solved be splitting stuff up.

@andrewnez I heard it works by just keeping a giant markdown file of all the prompts used to generate the code changes. You replay each prompt to get the diff of each commit.

@andrewnez Sapling gets callout, but… they didn’t use it?

Though admittedly the stuff that’s essential for monorepos (EdenFS) still proprietary