It comes down to the use case. For a collaborative editing software, yes we need all histories and a branches. But for configurations, it’s probably ok to forget old state and mutations don’t happen that often.
It comes down to the use case. For a collaborative editing software, yes we need all histories and a branches. But for configurations, it’s probably ok to forget old state and mutations don’t happen that often.
No replies yet.