When I reread this post an idea sprung in my brain: automatic version controls could be intermixed with backup schemes now that storage seems to grow (soon) to 80 petabyte on a common iPod
. (yes, we have left the terabyte age and are now entering the petabyte age) ( 1 petabyte = 1000 terabyte). I even wonder if it could be integrated in virtual machines.
But please note: automatic version control is not automatic configuration management, which is in the end a little block in this.
Meaning in the end: why don’t we just version anything and everything on any pc, laptop or any device and keep the history forever? Surely the exa-, zetta- or yota age will soon follow afterwards.
Putting meaning to the data, identifying branches etc… could be done by some smart tooling and some configuration files.
Currently you have to pinpoint the stuff that you want to be versioned e.g. some code, some documents, etc… When automatic version control would kick in, it would also register that you installed the little bug fix pack for tool Y on your system on day 25 and deinstalled it on day 26. IF, for some reason, everything goes down because of it, everyone will know who is to blame… hahaha.
p.s. this list is way cool “(1.25 terabytes) – capacity of a human being’s functional memory, according to Raymond Kurzweil in The Singularity Is Near, p. 126” which brings me to this totally unrelated, but still cool, image:
Which then again makes me think: when are we able to version control humans?

