What if it’s time to add features to the undo/redo construct as a whole? Maybe not discarding redo history when a modification is made in the past for example. Computers have improved a giant amount since undo was designed (clipboard too, for that matter). We should be redesigning these common* features to keep up with the times.
*often (not in MS Office probably) the undo buffer is managed by the OS. It’s conceivable that some rethinking could happen at the OS level.
vim 7+ keeps an ‘undo tree’ that permits this (it can also be instructed to keep it in a file to persist across sessions). It’s helpful to install a visualization extension to seek around easier (https://stackoverflow.com/questions/1088864/how-is-vims-undo...)
*often (not in MS Office probably) the undo buffer is managed by the OS. It’s conceivable that some rethinking could happen at the OS level.