I know some of classmates from college that used to refer to "GitHub" as "git" - that always kind of bothered me, but I didn't think it was worth my time to discuss with them.
This is incredibly common with recent grads in my experience. It's really quite frustrating for me because the organization I work for has code on both GitHub (open source) and private git servers. I have to spend half an hour or more with virtually every new intern explaining the difference.
Half an hour? All I can think of is: “git is a command-line program to manage source code. GitHub is a graphical user interface that builds on top of git, and adds some features like issue tracking. We installed git on our server. This is were we host our private source code. GitHub is the place where we host our open-source source code.”
Yes, half an hour is a bit more than just "git and GitHub are different things". It also includes a bit of explaining the basics of how git really works under the hood because I've found that users who don't make that distinction also don't really know what to do when something goes wrong. I try to get everyone to a point where they can resolve most common issues without resorting to mashing buttons at random in their GUI of choice.
Git is not most properly described as a command line program either. Git is a version control protocol/system for handling files across multiple locations. Github is just one of those locations
> Git is not most properly described as a command line program either. Git is a version control protocol/system for handling files across multiple locations. Github is just one of those locations
You're technically correct of course, but remember your audience (important pedagogical consideration). These are new grads that think git and github are synonymous. A slightly less technically correct but grokkable explanation is probably a better stepping stone toward arriving at a more correct understanding. You're description is abstract, which is harder to grok for most people than a concrete example. If you want to be more technically correct and therefore launch into a discussion about DAGs you're also not going to teach them anything.
Note: there are always exceptions, and a good teacher adapts to the audience. I'm referring to the very general case, not the exceptional case.
I really hope they are new grands in something not directly involving computers, because otherwise they would have to live in a cave to not know the difference between git and Github.
I was unclear about the fact that you can use them almost independently. I found that the first in this series of You Tube videos [0] made the difference very clear for me. Although his style might annoy some people, he made things pellucid. Perhaps only suitable for noobs. [0] - https://www.youtube.com/watch?v=BCQHnlnPusY
Sadly I actually use it as a way of testing intern applicants and even new grads as those that actually care to make any distinction between them (and I'm pretty lose with my criteria)...tend to be brighter or at least more aware of what they are doing.
In the case of GitNews, we can add any Git repositories from any sources. In the current version it's only from Github it's through but it may be extended to Gitlab and Bitbucket in the future or even Glitch.
I had several interviewees recently flub this in interviews. When asked about their experience with Version Control Systems they said they used "Github," not "Git." A bit of a warning sign.