...by being the first widely-available, free-as-in-beer-and-speech (and not under legal threat from AT&T) Unix-compatible OS.

...and that was most definitely not the first widely-available, free-as-in-beer-and-speech version control system capable of over-the-network access (and not, as far as I know, even the first widely-available, free-as-in-beer-and-speech distributed version control system).

(And it makes some things harder if you're "holding it wrong", but I digress.)

It's "just a technicality" in the sense that Android might not exist if Linux hadn't existed; saying that it's less relevant because people don't know it's there is like saying that ARM isn't all that important because most people don't know they have ARM processors in their smartphones. Git is even less directly relevant to most people, as they're not developers.

Presumably you meant "by creating Git"; as far as I know, he no more created GitHub than he created Android, even if GitHub uses Git and Android uses Linux.

Given that many projects don't use Git, I would not even come close to saying that Git is virtually indispensable in development (unless "virtually" means "not" or otherwise renders the adjective to which it refers meaningless).

I would say that some form of version control is important, but there were plenty of free-software version control systems, supporting over-the-Internet access, available before Git came along, so you can't give credit to Git for that.

I'd love to know the reasons that lead some to believe that "In some ways Git can be seen as his more important contribution".

SFW, as long as you aren't drinking anything you wouldn't want to spit up on your keyboard when you're reading it, otherwise your employer's IT department might not be happy about having to deal with the results of your spit-take.

Nope.

Given that this is a desktop environment for FreeBSD, atop which PC-BSD is based, not Linux (it might also work on Linux, but I presume that's not the primary goal), that's not relevant to this article (and also involves labeling a large number of significant and successful companies "insane", but that's probably your intent).

OK, so they're developing a BSD-licensed desktop environment atop a GPL v3/LGPL v2.1-licensed toolkit, right?

Who at Apple said that the new naming convention is "California surfing sites" rather than "California locations"? We only have one data point so far, and that's insufficient to conclude that the locations will all be surfing sites (or named after dogs or located in San Mateo or Santa Clara county or...).

And which I always do. Different strokes for different folks.

I use <code> too, if I'm posting code. Well, actually, I use <ecode>, because <code> appears not to honor line breaks and <ecode> appears not to honor indentation, and, for code, the latter sucks less than the former. Neither of them appear to provide me with any advantages if I'm just posting text.

The grandparent's signature line suggests he or she is making some sort of point about Javascript.

(Any objections containing the letters "e", "c", "m", and "a", regardless of capitalization, in sequence must be accompanied by an indication of why Javascript is different from ECMAscript in this context.)

Other big-box book retailers haven't succeeded at that, either.

But TFA seems to be talking more about independent bookstores than the "brick-and-mortar" chain bookstores that gave the independent bookstores trouble a while ago.

You're programming your drone in assembler language?

36-bit. There was also the 1620, which organized data as 4-bit decimal digits (with an extra flag bit and a parity bit); a character took two digits.