On Monday, October 27, 2014 5:05:55 AM UTC-4, Phillip Lord wrote: > > Fluid Dynamics <a209...@trbvm.com <javascript:>> writes: > > > On Saturday, October 25, 2014 10:42:24 PM UTC-4, tbc++ wrote: > >> > >> "What if my file had been corrupted, or truncated and only the first 42 > >> bytes of the new version written thus far, or something like that at > the > >> moment when the hang started?" > >> > >> So there's this new cool thing out there called a "version control > >> system". One of the more popular programs in this category is known as > >> git...check it out sometime, it'll help you relax when programming, > knowing > >> that previous versions of your file are only a few keystrokes away. > >> > > > > Besides, it's stupid to expect everyone to use a version control > > system, particularly just to ward against bugs that have no business > > existing in the first place. > > Actually, no, it's not. Using a VC system is something that more or less > every programmer should do. Combined with backups which, no doubt you > do, it makes the possibility of loosing work through someone elses fault > quite remote. A VC with a number back-up save function on your IDE is > the way to go. > I'm not going through the ritual of check-in and check-back-out every single time I'd normally hit control-S. Too much friction, too much work-that-isn't-development.
> Really, you expect me to create an account and publish every little > > bit of code I play around with on github? > > Publication of code for VCS isn't really necessary. RCS which was > released in 1982 didn't require it (actually, didn't support it). With > the advent of DVCS, it's not needed now. > Objection: relevance? The OP specifically suggested github, > Sometimes I write some function or big static map or vector or > > something out a line at a time, saving every couple of minutes or if I > > pause for any reason. I'm certainly not about to commit code in such a > > state to a VCS, let alone publish it where others can see it. > > That's what rebasing is for, although I agree it doesn't avoid the > usefulness of a numbered backup. > I don't even know what "rebasing" is. I'd much rather not have to either, not when my current workflow is fine for me just so long as my tools have the courtesy not to threaten to crash in the middle of a save. How many hours, weeks, or months of ascending some no-doubt-steep learning curve would be involved in following your recommendation? Would I be able to resume making forward progress on my actual project by Christmas, or would it be closer to Valentine's Day? -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
