The comment you're replying to mentions some limitations of the current state of the art.

I agree that there's no reason to change just because something is older than some threshold. Bit I think the roughly 15 year cadence has reflected the time it has taken for a new VCS idea to develop and then become mainstream enough for its drawbacks to become annoying enough that it loops again.

I don't know about that. The UX of git leaves a lot to be desired. monorepos and large files are not definitely solved, either. If not git, what solution did you have in mind?

millions of repos on github don't have those issues.

Youre talking an extreme use case. Like saying we need to replace the shovel because it cant do what a bulldozer does.

Its miniscule fraction of GitHub repos have those issues like an incredibly small number mainly devoted to games or media.

UX is fine if you know it. SQL UX isnt ideal either.