3 ms·
I commit to version control very often. Further, with version control, you annotate the commits with meaningful messages, and you (presumably) commit at meanin
by Pistos2 17y ago
I commit to version control very often. Further, with version control, you annotate the commits with meaningful messages, and you (presumably) commit at meaningful points in time. For example, you (usually) wouldn't commit in the middle of developing something (when it's obviously broken, even syntactically). Snapshooting at arbitrary points in time would not enjoy these benefits of intentional version control commission.
- acangiano 17y agoI'm obviously not arguing in favour of replacing git, hg or svn with this. It would be a fun, additional feature to have. You could then watch how the code evolved over time, easily move step-by-step, hand it over to a less experienced developer to teach him how to refactor code, and so on. I would find it useful.
- akkartik 17y agoThat mirrors how I hack. I like to think in terms of the changelog message, what I want to say about the current snapshot, front and center. The fact that the snapshot is saved at that point is almost implicit. http://akkartik.name/codelog.html http://akkartik.name/codelog.html (from 2005; now I use git instead of darcs)