3 ms·

As what point does a fully featured undo/redo system start to look like git (/VCS of choice)? Once you add deliberate checkpoints and the tree structure from t

• afc 3y ago
  This resonates with me. I use undo/redo up to a point, but eventually I just reload the file (which I'm saving frequently) or just check it out (from git, mercurial) again.
  • truculent 3y ago
    Right - using undo/redo for quick or ephemeral changes, before solidifying into something (more) permanent feels very similar to me to making a bunch of small commits while working on/exploring something before cleaning them up into semantic chunks with a rebase. Maybe there’s some implicit idea here like treating a commit as an aggregate of a bunch of atomic actions (i.e what undo/redo act on)
• sureglymop 3y ago
  As a music producer who has been working with various DAWs, I've always been super jealous that programmers have git. Not just for version control but also for collaborations. I always thought, it must be possible because sound is just a list of samples (numbers). Kind of like how a binary executable or assembly code is just a list of values or instructions. Unfortunately most music software and plugins are proprietary as this industry did not have the same political movements (GNU, F(L)OSS, OSS, etc) that the computer industry had and most professional software has been created for professionals by companies. It's interesting though because software like Ableton Live has an unlimited undo history but since it is proprietary one can't really look at it.