Re: RedyCode 0.9.3
- Posted by jimcbrown (admin) Jul 21, 2016
- 2013 views
Actually, there is. The date stamp allows one to discern statistics related to time (when did I work on it, how much progress did I make that day, that week, etc.). The sequential indicator is much easier to track milestones with.
The date becomes the milestone. The sequential number is redundant.
Depends on the preferences of the user.
For example, it's easier to tell the number of revisions between euphoric.exu.20160721101010.00098 and euphoric.exu.20160721232323.01198, than it is with just euphoric.exu.20160721101010 and euphoric.exu.20160721232323. Of course it's really easy to figure out with the right tools either way, but with the latter it's a lot harder to just plain eyeball the answer.
Heck, if you are going to call me out on redundancy we don't need either as the operating system will timestamp the file.
You need filename differentiation, so the timestamp won't suffice.
In some cases that's not enough.
If one lives in a timezone that observes DST and likes to code in the middle of the night, then - in the fall, when we all go an hour back - the hour of 1am repeats. So you might have euphoric.exu.20151101013030 (for 01:30:30am EDT on Nov 1st, before the DST switchover, or 05:30:30am UTC) and later have the bad luck to make euphoric.exu.20151101013030 again exactly one hour later (on 01:30:30am EST after the DST switchover, or 06:30:30am UTC).
Even if you avoid saving two backups with the exact same file name, the names are no longer ordered - euphoric.exu.201511014324 may have been the earlier version and euphoric.201511011216 the later backup.
The other case is if one is traveling and changing timezones. Even saving the 3 letter timezone acronym here is not enough, as some timezones share the same acronym (such as AST for Alantic Standard Time and Arabia Standard Time).
