Handling History in Software
  • most software currently supports only linear history
  • exceptions are vim and emacs which provide tree-like undo history, where every change creates a branch:
    undo-tree in emacs
  • git does something similar, but is far from accessible
  • web browsers should be great at this, but fail all the time
  • history could be browsable
  • history of changes is another example of sequences of static snapshots
  • CLIs allow users to see the history of query -> result
  • exploring links is related to browsing, and to be able to do that freely - to history
  • history of changes is not tackled well - I want a graph with previews, not undo/redo stack
Szymon Kaliski © 2020
mailtwittergithubwebring