I took a drivers ed class where we had a steering wheel contoller and pedals hooked up to a computer. It was essentially a really boring version of Cruisin' USA where we had to go from point A to B while staying in the lines and stopping at stop signs. We eventually did get to pilot a real car after several weeks.
This was back in the late 90s in the Midwest of the US.
I'm going to have to respectfully disagree with you there. If you're having to research the history of the phrase, you're overthinking it. It means exactly what it states, no tricks. "Free speech" is a well known phrase that means the unencumbered ability to say what you like. "Free beer" means something that everyone (ostensibly) likes being handed out without the need for payment. I'm not sure how one could more simply explain the "free" dichotomy. If you've got a suggestion, I'm open to hearing it.
I guess I don't understand the question. Plenty of open-source projects charge money for a license. And even closed-source / non-free games have pirates. The availability of the soucre code does not determine a business model, the licensing does.
What are the jargon words youre referring to? In my experience, it uses the same jargon as the other VCSs.
Perhaps you have a different workflow than me, but I don't find myself rebasing all that often to begin with. I generally don't rewrite history unless I truly fucked up. And since I'm in "I fucked up" mode, I take extra care with commands I type.
I don't wanna be like Apple and say "You're holding the phone wrong," but maybe you shouldn't be doing frivolous rebasing.
If it's an issue of having to read the docs or the man, well I've been at work like this for a little over a decade and I still have to pull up a reference when I want to do something nontrivial in, not only git, but pretty much every cli tool I use on a regular basis. Cli tools, frameworks, libraries, languages... I have to pull up a reference for everything I do as a programmer, so it's hard for me to muster up the indignity for having to look up how git works.
If it's a matter of understanding the flow of the tool, then I will have to concede that mercurial probably is easier to understand for the beginner.
This seems like putting a training wheel on a training wheel. git is already the easiest to understand of any VCS that I've used, and it's somewhat hard to do something in git that can't be reversed. As the articles states, it's unlikely you'll ever lose your changes. Further, this doesn't seem to be that different of a concept from git reset, so why not learn reset instead of yet another command?