He is an amazing dev, don't get me wrong. BUT he had lots of luck starting from not choosing the name Freax, choosing the same license as his compiler (GPL), and a professor that did no understood free-software (Tannenbaum and his minix), the legal battle of the BSD's...and maybe a too expensive and ~slow solaris, and a really good but proprietary VCS (Bitkeeper) as a idea-blueprint for git.
But, tens of thousands of other people had all of those same lucky things.
Linus has claimed to have been unaware of the existence of BSD, so perhaps he had a bit of fortunate ignorance as well.
(FWIW, neither Linux nor git are my preferred options, but I still think Linus has spawned great things. :)
https://news.ycombinator.com/item?id=8641073
https://groups.google.com/forum/#!msg/comp.os.minix/dlNtH7RR...
>But, tens of thousands of other people had all of those same lucky things.
Yes AND?
>but I still think Linus has spawned great things.
I did not say anything else.
Linus is also lucky that he had decent nutrition in his childhood, and that Finland was not at war with Russia during his university years. He had the luck to be born to parents that were able to prioritize education over subsistence. So yes, he was lucky.
But in your previous comment, you also call Linus's choices "luck". That doesn't read fairly to me.
He had the luck to make good choices? Maybe in retrospect, but you must acknowledge that there's much more than luck involved.
Of the tens of thousands of people with enough "luck" to arrive at roughly the same place in 1991 -- by which I mean smart, well-fed, decent academic/life schedule with adequate free time, few or manageable commitments like spouses/dependent children or parents, broad and deep exposure to Unix, access to USENET and the Internet -- Linus remains exceptional.
My closing parenthetical was not a counterpoint to your message. It was to frame my perspective: I don't worship, but I do respect.
There where not "tens of thousands" peoples who made a ~unix kernel licensed with the GPL.
>Linus is also lucky that he had decent nutrition in his childhood
Yeah let's stop here it getting stupid.
Among the tens of thousands who were in the right place, single-digit dozens made the attempt, and only Linus succeeded in such a visible way. If you want to argue that he was merely the lucky one among dozens, then you still have a lot of extraordinary evidence to present, but you might have an interesting story to tell.
Your original comment reads like a dismissal because Linus drew inspiration from the world he lived in, and was just "lucky".
The point is that he did the work, he attracted the community, he managed the project. None of that was luck. And none of that is highly correlated with being an "amazing dev". Of course he stood on the shoulders of giants. Of course he learned from (and drew from) the environment around him. Of course Linux would be a forgotten academic project without the GNU userland (and license, maybe). Etc etc.
We all lived in that soup. Linus did the hard work and made something from it. I thought your comment was highly uncharitable in its disregard for all of things that made Linux successful.
> Yeah let's stop here it getting stupid.
On this, we can agree.
To be honest, for most purposes, shared docs do revision control well enough for the purposes of text docs and presentations. I've used GitHub for some larger collaborations, but it's really overkill for most day-to-day docs.
I don't think that is necessarily due to not be able to use git (as in not competent to use it) but not able to use it due to restrictions in their workplace or even just unfamiliarity with the possibility of such a tool existing.
I think you'd need an extremely good GUI if you wanted to market git to the masses.
Git always felt more like you were exposed a raw low level API on the command line with a few shell macros on top to make it a bit more palatable which is effectively what it was for a long time. I suppose it fits well within the unix philosophy of clunky but very flexible and not very opinionated tools.
Every time I do something more than that I end up needing to google error messages, and usually end up copying my changes to a temp directory, doing a hard reset, and starting over.
pull should’ve been clone.
commit should’ve been snap.
push should’ve been commit.
This way, clone (instead of pull) will make a local copy on your computer.
This is your local working copy. When you are ready to save, you can “snap” shot it, and leave a little message. And you can do as much of this as you want.
Then when you’re ready to merge it back to the primary database, then you can “commit” it.
The whole concept of pull/commit/push seems nonsensical to me. As a layman, I can’t understand the importance of pull vs. push in this context. And this makes it difficult to explain to someone non-technical.
I wish all the time that more of the people I know outside of software could benefit from something like Git. It's unbelievable how powerful a tool it is, and when I watch people doing awkward and error prone simultaneous-editing and remote synching etc, it just doesn't compare.
But then git is too abstract for many. Your files are a representation of a state of combined changes, the files themselves are not the owners of their content.
I even had to have a huge debate with a developer once about how storing a git repo in Dropbox folder so they could have same exact state across two machines was a terrible idea, and already solved with Git itself...
And then how few people also know how many places the Linux kernel or derivatives live, or even that many things they use are running something based on Linux.
What an incomprehensibly huge achievement on both counts!
[Edit] typo