@poisonBar
imagine being so badass and confident as Linus. You cut me off! no, I cut you down
@tamantaman
10 days. Let's think about it the next time we find ourself stuck on a web button for weeks 🥴
@patcoston
Amazing that Linus Torvalds created world-changing Linux then later created world-changing Git. I wonder if he will create a third world-changing piece of software.
@RichardHoule
3:57 “Reinventing Version Control” The problem I have with this statement is that’s it’s not entirely true. Linus took a look at all the possible alternatives, figure out that they all had a least, one bug or missing feature that was a must for him, and he went on to create git with all the ceoncept and designs he liked left and right.
@OgbondSandvol
This guy who created Git is very skilled. I wonder what he could have achieved if he ever tried to make an operating system kernel.
@VeitLehmann
In the age of AI assisted/driven development, version control is more important than ever, and Git still does that job best. Less people might interact with Git directly, but I think the core of it will be here to stay for many years to come.
@RogerValor
SVN had branches, mercurial was also spawned around that time, and bzr was also very popular for a while. Also, it was not 10, it was 15 days until the first merge succeeded, and 3 months until the first official usage. Torvalds for sure did this in a phenomenal timeframe, but I think overselling it is not necessary, even stemming this in 3 months into being used in production was a feat.
@Ghandmann1
The blockchain question ist hillarious. Since git is actually a blockchain. Bitcoin was heavily influenced by the way git links its commits (aka blocks) via commit-hashes. The only basic difference: Git does not require proof-of-work, since it is not an autonomous system which requires a consense mechanism.
@RichardHoule
4:40 Git secret weapon was… branching? Branches existed LONG before Git. Same with snapshots. Git wasn’t the first projects to have that capability.
@patcoston
4:20 Git does not always resolve conflicts automatically. Some merge conflicts need to be resolved manually. There is no way for Git to know how to merge certain types of conflicts.
@side2k
Meanwhile, CEO of BitMover: "Linus was able to build it in 10 days! With a box of scraps!"
@davidmacly
The production value on this is insane for how many subscribers you’re at, keep up the good work!
@dondekeeper2943
Many facts are either misrepresented or exaggerated. Git is technically just an OSS clone of bitkeeper, with a few Linus-touch here and there. BTW, Mercurial is NOT one of the "older systems", it's born around the same time as git with similar features/capabilities and far more user friendly in the early days. Git is only more popular due to Linus, Linux and github.
@sajibprime3
0:22 "But how did one man" - bruh , That one man is linus torvalds, The man who made the whole linux ecosystem possible.
@nfinzer22
You should have talked about its competitor mercurial in the early days of DVCS
@bauckrob
If you want to tell about how Git won, you also have to tell about the alternatives and why they didn't win: Mercurial, Darcs, Bazaar, Monotone. Most of the different systems used a command line interface with the same commands introduced by CVS and Subversion. That was not the issue about Git's reputation for being hard. Rather it was that central concepts was chained on as command line parameters to other commands in not so logical places, and that these commands then had very different meanings based on these switches. E.g. you would use the checkout command to check out a revision from the repo, or with -b you just create a branch. What's the opposite of push? Yes, that would be fetch. Replace git with blockchain? Git is blockchain: The commits are securely linked to previous commits with cryptographic hashes, and the commits are represented as Merkle trees of directories and files.
@VectorNodes
3:25 is sacle something I’m out of the loop on, or a legit typo?
@QuicksilverSG
Git was by far the source of the worst crap I had to deal with at the end of my 40-year career in software engineering. It is the epitome of the reinvent-everything-yourself syndrome that afflicts every corner of "modern" software development. It's such a relief knowing I'll never have to plow through yet another obsessively forked repository again.
@Jagi125
"Steep learning curve like knowing command line." Man, if you're programming and don't know at least basics of using terminal programs, I doubt you can actually program.
@CodeSource