steveklabnik

Yeah, I'm not saying C does, just that Rust's features aren't limited to "helping you with heap memory." Rust is also more than lifetimes.

Rust doesn't have heap allocation in the language at all. It still has useful features regardless.

> Rust has no reason to touch the original Unix API.

As a systems language, Rust must provide access to the APIs of the underlying system, and on UNIX, that’s, well, UNIX.

I was born in Butler!

Okay, yes, I agree that that’s how it works. I thought when you said MUST you meant that it doesn’t work; it does work it’s just that it burns a turn or two to do the lookup there. I certainly agree it would be nice to not do so.

(And I didn’t know the double args thing, that’s very interesting! I should have said I only meant the first bit.)

The 30,000 number is across their entire monorepo, which they say in the article Claude Code does not live in.

I have done exactly this as recently as yesterday, so I’m not sure why it doesn’t work for you.

It also did find bugs in the old code and contributed tests to their suite.

Makes sense, all I wanted to point out is that this is a real problem for some real companies.

It is sort of semi-ironic to suggest this in this thread, but you can ask Claude about why Facebook created Mononoke and Sapling, and where git has scaling issues. It will give you good answers.

Microsoft did, but that doesn't change the limitations imposed by git's design. Their repos just weren't as large.

> under 1 commit per second

Sure, for arbitrary pushes, that's not a big deal. But for large repositories, with those changes landing on trunk at that rate, once you start talking about "commits per second" it gets very difficult.

To be clear, we are not building a build system, just a VCS. :) we do use buck2 internally though.

I do care about Windows, having used it for years at this point. The client is git or jj, so Windows support is there for sure. For some of the other stuff we’re doing, we’ll see what customer demand is like. Obviously there are tons of devs on Windows, but we also have to make calls about priorities too.

Google and Meta hit these sorts of limits over a decade ago. They then built new VCS stuff to handle it, Meta's part is the subject of this submission. This was even pre-agents.

Git is just not suited to truly large monorepos, and it won't ever be. That's totally fine, of course. Less of a monoculture here would be great.

Rust NYC is certainly one of the things I have missed since moving to Austin :)

Maybe, we'll see. I think one thing that's tricky these days with startups is that being super transparent technically about what you're up to is much harder to justify. Look what happened with Origin: tobi vibed up a copy over the weekend after it was announced. Obviously there's balance to be found here, but that's partially why we play our cards a little closer to our chest.