This still sounds like a case of "I haven't learned how to use git yet, and although that means I can't possibly understand how it might improve my workflow, I don't want to take the time to learn a fundamental piece of software that's used by the vast majority of the programming community."
On Tuesday, October 28, 2014 5:14:45 PM UTC-4, Fluid Dynamics wrote: > > On Tuesday, October 28, 2014 5:01:47 PM UTC-4, Charlie Griefer wrote: >> >> >> On Oct 28, 2014, at 1:28 PM, Fluid Dynamics <a209...@trbvm.com> wrote: >> >> Meanwhile, I think some people still have not grasped the scale of what >> I'm doing, namely how small it is. Small, experimental, limited to one >> person, and so forth. Version control, I repeat, would be MASSIVE overkill >> under the circumstances. It would make barely any less sense to reach for >> version control before writing a "hello, world" program. >> >> IF the project grows enough and is successful enough, then I might >> consider creating a github account and basing it there. >> >> >> As has been mentioned already, git != github. >> >> Really, if the risk of losing your changes to this file are enough to >> warrant the tirade that you’ve been on, it’s enough of a risk to warrant >> doing a git init in the directory. >> > > It's not "doing a git init" that concerns me. It's: > * Finding and installing yet another piece of software > * Learning at least the basic ins and outs of that piece of software > * Configuring it, since it sounds like commandline stuff that probably > does not simply work OOTB without setting PATH and probably fiddling with > other things > * Figuring out how to configure CCW to integrate with that other piece of > software -- if that's even possible > * Manually mucking about checking out, copying the files into CCW's > workspace, and later copying the files back out and checking in if not > * Extra steps around every file save or open, namely whatever is needed to > do checkins and checkouts from version control. > * Dealing with whatever subset actually happens of the new > things-that-can-go-wrong that get introduced by all this added complexity. > > One warning flag already apparent is the very phrase "doing a git init in > the directory" in your post. Sounds like I'd be having to do a lot more > fiddling around at the command line than I currently do. Infinitely more, > in fact, since the current amount is zero. :) > > I remain wholly unconvinced that it's worth the hassle for a project this > small. > > -- 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.
