5 ms·
Nice formatting aside, I am slightly concerned that GitHub "releasing a release note" for Git would further blur the distinction between the two for new program
by paradite 10y ago
Nice formatting aside, I am slightly concerned that GitHub "releasing a release note" for Git would further blur the distinction between the two for new programmers.
If I were new to Git and GitHub, I would have thought that Git is a product of the company GitHub.
Edit: After searching through git repo and official site, I could not find any nicely "rendered" release note beyond the official release note in raw markdown here: https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.10.0.txt https://raw.githubusercontent.com/git/git/master/Documentati... , so I think GitHub is doing us a good thing here by giving a high level summary and actually rendering the markdown properly.
- rickycook 10y agoi assume that's at least partly intentional from the github point of view
- danso 10y agoOh geez, you're giving me flashbacks to trying to introduce Github to non-technical students. I basically just don't even try to explain the difference, because I have them use a minimal set of git's functionality, that is, the subcommands add, commit, and push...and of course, clone and init at the beginning of the quarter. And I teach them virtually nothing about Github other than that it's a website that you interface with git. For me, Github is a great place to get students to push their assignments and papers because I can easily comment on them...once in awhile I'll do a force push to fix something. We never do anything with forking, and I strongly discourage them from using the Github web interface to edit documents, as that is the most frequent cause of merge conflicts. If they follow what I say, git and Github are just glorified document-uploading systems. I've almost never had a student fuck up in a way that we had to rollback something, because for the most part, people who don't use version control as their job don't need it. Version control is only particularly relevant when working in a team, doing iterative work, or deploying to multiple environments. These are things that students do not need to worry about. And actually, even the comsci students don't really need to worry about it. If I do attempt to explain the difference between git and Github, I usually use the analogy of git is to Github as your cameraphone is to Instagram.
- cglee 10y agoIf you ever run into this need again, I'd recommend this book: https://launchschool.com/books/git https://launchschool.com/books/git
- paradite 10y agoThanks. I often have troubles explaining to others the difference between Git and GitHub, and I think the camera phone and Instagram is a nice analogy.
- noufalibrahim 10y agoI do corporate trainings on git. Many prospective clients or vendors call me asking for "g.i.t. hub" trainings. Thankfully though, most of these are just the misinformed marketing teams. The engineering people usually grasp the difference easily when I finally reach the parts about collaboration. I like the cameraphone/instagram analogy. Thanks! I usually do all the pushes/pulls etc. using a file:// remote so that people can see what happens and then just tell them that github is what happens with you move the remote to the cloud and give it a nice UI.
- deevus 10y agoInteresting. Do you get a lot of work training people in git?
- noufalibrahim 10y agoIt's reduced a little in the past few months. I've increased my rates a little so that I can focus only on direct clients rather than training vendors who need the prices to be low so that they can take a cut. Also, I think cheaper git trainers have shown up on the market and many people are already familiar with it both of which have reduced the number of requests I get.
- jghn 10y agoI recently participated in a focus group which was discussing git, github, and other git-ish things. To my eyes, it seemed like most of the other participants were unclear on what the difference between git and github actually was as answers about the two were often interchanged.
- saurik 10y agoIn a more perfect world I would have wanted to see GitHub be stopped at the time of release due to trademark concerns, as they clearly did this knowing it would creat this kind of confusion; it devalues git itself and their business model relies on that.
- ugexe 10y agoThat's quite an extraordinary claim. Do you have any actual evidence to support it?
- saurik 10y agoTo support which claim? That they knew naming their product "GitHub" would lead to this kind of confusion? The opposite of that is the extraordinary claim: it is painfully obvious that if you take someone else's product and name yours "ThatProductHub" you will cause semantic confusion over whether your product is directly affiliated with the other product. I am not even sure what evidence could be provided to refute that claim other than a record of extremely low IQ scores :(. People do this because they want to ride on the coat tails of the other brand, whether they want to admit it or not.
- oldmanjay 10y agoTo be fair, I'll point out that you are giving no consideration to the fact that git's popularity is due in part to GitHub's massive success and that the relationship is clearly mutually beneficial.