A blog post isn’t quite the format in which to go into the length details of why, so it sufficeth me to say that Git is great source control software. Local commits. 1 command to initialize a repo. Branching and merging isn’t so ridiculous that you never do it.
GitHub also seems pretty neat, though I confess to be a GitHub newb (or noob– I forget which is derogatory. I don’t mean that one). GitHub allows free hosting of open-source Git repositories. I don’t really plan on making the project I’m working on open source– and for no particular reason– so that’ll get changed when I want to close things down. It does cost money to host closed-source projects. Point being, off-site backup is a Good Thing, a quality especially noticeable when one accidental rm -Rf’s their repository. Oops. Good thing I had basically only clicked New Project in Visual Studio.
So, this post is supposed to matter because you get some useful information and not just some narcissism. If you’re a Windows user at least part of the time, it’s readily apparent that Git wasn’t written for Windows users. Do the author check. It’s slightly confusing to get Git working, and rather than re-invent the wheel– though I’m not afraid of beating dead clichés– checkout the work of some dude named Kyle Cordes.
His post works as advertised. I did skip all the bit about being added to his repository, as I wanted to do my own. Also, I stopped the whole thing at “Approach 1: GUI.” It was pretty easy getting the repo into git-hub by following git-hub’s instructions.