Archive for August, 2008

Present reality vs. future possibility

August 14th, 2008

I’m listening to the radio this morning, and in a news segment there was a little blurb about John McCain choosing a so-called pro-choice running mate.  The announcer then made a mention of abortion “rights.”

Being one who chooses to err on the side of life, I have a big issue when someone talks about abortion “rights.”  America has a duty to protect her citizens, and the unborn certainly don’t have the capability to speak up for themselves.  Just as I feel we should reinstitute usury laws to help protect the financially weak (the lack of such laws unfairly harming minorities), I feel we should protect a child who happens to reside within his/her mother’s womb.  Where do their rights factor into abortion “rights?”  But that really isn’t the issue of this post.

I’ve read so-called pro-choice advocates argument that a mother is here now, and a child is only a possiblity in the future, so society must err on the mother’s side when making this choice.  That is certainly a sound argument (sound = the conclusion follows the premise, regardless of whether or not the premise is flawed;  it’s a logically consistent position).

So let’s take that sound argument to another issue of the day.  Global Warming.  The proselytes of the Church of Global Warming warn us of a Vengeful God that will strike at us if we don’t do “something.”  They propose policies that would bankrupt our nation and cost lives now all for the sake of some future possibility.

So which is it?  Does a certain present automatically override possible futures?  Or is just that progressive folk have chosen certain issues about which they feel passionate?

Look, as a conservative, I actually do respect the sound arguments of others.  I’m just asking for some consistency here.

Git, GitHub, and Windows

August 4th, 2008

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.