I built a prototype, and then I rebuilt and rebuilt it and rebuilt it, and somewhere in there my understanding of how to think about what I was building completely flipped on its head. Then I rebuilt the version flipped on its head another several times until I finally understood it. You can see that on my Github, it's all public: https://github.com/conartist6 (public devlog on Discord).

It's a pretty serious claim to know what comes after git, and I have a whole array of criteria I evaluate claimants on:

- Will their version control solution fall apart if there are not enough line breaks in the code?

- Can they solve the rename-function/add-usage conflict? Git normally can't surface this conflict at all.

- Can the system maintain authorship attribution at a fine-grained level (per-second resolution)

- Will their solution's performance break down if there is too much code in one file?

- How will the solution handle change notifications? Is the filesystem watcher the de-facto coordinator?

This GitButler thing fails all my tests for a thing that's serious about replacing git; it just seems like they haven't thought about any of that stuff, well, at all.