Some Actions overwrite other Actions. If we calculate all Actions in a History, then we waste resources, especially as the History grows. Here are some options, including a discussion of pros and cons.
Compress-on-read: Requires that Actions don't encode large data. Preserves full Undo and Immutability. Scaling issue In the worst case.
Compress-on-write: Loss of Immutability. Loss of infinite Undo.
Compress-on-write of history-tail (preserving first 100 Actions): Disadvantages and advantages of both.
Some Actions overwrite other Actions. If we calculate all Actions in a History, then we waste resources, especially as the History grows. Here are some options, including a discussion of pros and cons.
Will inititally implement compress-on-read.