Eventually someone will make a Desktop Linux distro that targets macos exiles, using macos keybindings everywhere. When that day comes, I will be back on Linux like a shot.
I found the virtual branches compelling, but when I tried it out, I got myself into a mess.
I think that this could all be done using real branches, plus an integration branch with post-commit hooks to backport each commit onto the "default" branch and recreate the octopus merge "integration" commit each time. Would that work, or am I missing something?
I recently spent multiple months building out something like this blog post describes, for a notion-like app (to replace a different versioning scheme that could do draft pages but not point in time viewing).
We ended up doing it all in typescript, or with some postgraphile shenanigans.
One of the things we missed when requirements gathering was the ability to view a table of records each at their "latest published" version.
I think this can probably be done by including a pair of tztsrange columns in the history table (one for "when was this the latest valid draft?" and one for "when was this the latest valid published version", and do a bunch of date shuffling whenever you publish a version.
We've not actually done this yet, because there are some edge cases around dependency graphs and computed columns, but for a simpler app I reckon it would work just fine.
Recently I have been using SD 1.5 checkpoints with the LCM lora for all of my image generation (generally weighted down to 0.8 strength, with 6 step inference). It's not as fast as sdxl turbo, but at least it does a good job of people's faces.
It would be good to make more efficient use of people's donated resources by making it possible to use LCM lora.