[dist-epoch]

GitHub is not agent scale.

Multiple companies are trying to create new versioning primitives/architectures which can handle machine-level code generation - 1 commit per second per repo.

It's like switching from horse buggies to automobiles, the whole worlds needs re-architecturing to handle the new load.

The age of boutique hand-coding is being replaced by the age of industrial software factories.

[swiftcoder]

> new versioning primitives/architectures which can handle machine-level code generation - 1 commit per second per repo.

This is not a particularly novel level of scale. Facebook's mercurial backend had to handle >5,000 developers committing to the singular monorepo long before LLMs were a thing

[KptMarchewa]

Yes, on a single repo. Now multiply that per bazillion companies on github, some of which are trying that.

[julianlam]

Why the heck would you want to do this. Using git as your undo chain sounds like a pretty awful thing to do.

[dpkirchner]

I think it'd be pretty neat to be able to rebase my undo history on to a remote branch someone else is working on.

[fapjacks]

This is smart but also hilarious.

[skinfaxi]

This seems odd to me. Why would you need to commit every second?

[gedy]

And push to remote as well? Seems not thought out

[andyjohnson0]

> GitHub is not agent scale.

Is the scaling issue with git or github?