Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

When did Git go from "too different" to the industry standard? 🤔 Linus Torvalds explains the generational shift that changed everything—when young developers started with Git as their first SCM, making it the default. Learn more about the history of Git in our full interview with Linus. ⬇️

GitHub

2,627,380 subscribers

48,478 views • 11 months ago •via X (Twitter)

Science & Technology News & Politics Education

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Linus Torvalds remembers those first reactions to the Git interface. 👀 Here's why he did things differently when launching the version control system we know and love today. ▶️ Learn more about the early days of Git in our full interview. 🎙️ ⬇️

Linus Torvalds remembers those first reactions to the Git interface. 👀 Here's why he did things differently when launching the version control system we know and love today. ▶️ Learn more about the early days of Git in our full interview. 🎙️ ⬇️

GitHub

79,319 views • 9 months ago

⭐ In 2005, Git made its first commit. ⏩ Fast-forward to 2025, we relive the birth of Git with the creator, Linus Torvalds. ❤️ Head down memory lane with us.

⭐ In 2005, Git made its first commit. ⏩ Fast-forward to 2025, we relive the birth of Git with the creator, Linus Torvalds. ❤️ Head down memory lane with us.

GitHub

257,798 views • 1 year ago

Git really is for everyone. Creator Linus Torvalds explains why. 👀 Check out our full interview for Git's 20th anniversary. 👇

Git really is for everyone. Creator Linus Torvalds explains why. 👀 Check out our full interview for Git's 20th anniversary. 👇

GitHub

27,022 views • 1 year ago

Was Git built in 10 days? Linus Torvalds tells us the real story. 👀 Watch the full interview in honor of Git's 20th anniversary here.👇

Was Git built in 10 days? Linus Torvalds tells us the real story. 👀 Watch the full interview in honor of Git's 20th anniversary here.👇

GitHub

31,702 views • 1 year ago

The problem: Applying patches was painfully slow. 🐢 The solution: Build a tool so good at merging you barely need patches. 🤝 The result: Git. 🏆 Hear more stories from Linus Torvalds in our interview for Git’s 20th anniversary. ⬇️

The problem: Applying patches was painfully slow. 🐢 The solution: Build a tool so good at merging you barely need patches. 🤝 The result: Git. 🏆 Hear more stories from Linus Torvalds in our interview for Git’s 20th anniversary. ⬇️

GitHub

38,879 views • 1 year ago

Linus Torvalds created one of the world's most important operating systems—but is he known more for the software he only maintained for a couple of months? 👀 Find out more from our conversation for Git's 20th anniversary. ⬇️

Linus Torvalds created one of the world's most important operating systems—but is he known more for the software he only maintained for a couple of months? 👀 Find out more from our conversation for Git's 20th anniversary. ⬇️

GitHub

45,498 views • 1 year ago

Did you know that you can visualize Git operations in your repos with Initial Commit's git-sim? Generate images or videos to help you understand how Git works, or just show off in your next standup!

Did you know that you can visualize Git operations in your repos with Initial Commit's git-sim? Generate images or videos to help you understand how Git works, or just show off in your next standup!

GitHub

150,142 views • 3 years ago

THE GUY WHO BUILT GIT GAVE A FULL LECTURE AT GOOGLE BECAUSE 99% OF DEVELOPERS USE IT WRONG 70 minutes of pure firepower from Linus Torvalds himself - the man who wrote both Linux and Git from scratch. -> The moment you watch it, you realize why "I'll just figure out merge conflicts on the job" is the dumbest sentence in modern software engineering. He spends the first 10 minutes calling out every other version control system in existence and he's not joking. He literally tells Google engineers using Perforce to find a new tool. Git isn't a "nice-to-have" anymore -> it's the operating system of every codebase you'll ever touch. If the man who built it had to explain it to a room full of Google engineers, you don't get a pass either. Don't forget to bookmark & watch it today.

THE GUY WHO BUILT GIT GAVE A FULL LECTURE AT GOOGLE BECAUSE 99% OF DEVELOPERS USE IT WRONG 70 minutes of pure firepower from Linus Torvalds himself - the man who wrote both Linux and Git from scratch. -> The moment you watch it, you realize why "I'll just figure out merge conflicts on the job" is the dumbest sentence in modern software engineering. He spends the first 10 minutes calling out every other version control system in existence and he's not joking. He literally tells Google engineers using Perforce to find a new tool. Git isn't a "nice-to-have" anymore -> it's the operating system of every codebase you'll ever touch. If the man who built it had to explain it to a room full of Google engineers, you don't get a pass either. Don't forget to bookmark & watch it today.

slash1s

214,857 views • 2 months ago

The New GitHub Innovation Graph data shows the EU overtaking the US in git pushes. 📊 How else is the global developer landscape shifting? 🤔 Explore 5 years of trends ⬇️

The New GitHub Innovation Graph data shows the EU overtaking the US in git pushes. 📊 How else is the global developer landscape shifting? 🤔 Explore 5 years of trends ⬇️

GitHub

70,917 views • 1 year ago

It's back! 👀 The GitHub Innovation Graph has been updated with fresh data. 📊 Find out who's leading in git pushes, repositories, developers, and organizations. 🏎️

It's back! 👀 The GitHub Innovation Graph has been updated with fresh data. 📊 Find out who's leading in git pushes, repositories, developers, and organizations. 🏎️

GitHub

103,732 views • 6 months ago

You don't need to memorize a dozen Git commands on day one. Start with the visual tools in VS Code, learn what commits and branches actually do, and build from there. That's exactly what we're covering in our latest GitHub for Beginners episode.

You don't need to memorize a dozen Git commands on day one. Start with the visual tools in VS Code, learn what commits and branches actually do, and build from there. That's exactly what we're covering in our latest GitHub for Beginners episode.

GitHub

24,609 views • 2 months ago

Git Merge vs. Rebase vs. Squash Commit What are the differences and when should you use each? As I explain in more detail in the video, there are some key distinctions. Git Merge This creates a new commit in the target branch. The new commit ties the histories of both main and feature branches together. Git merge is non-destructive - it introduces a new commit without altering existing ones. Git Rebase Rebase transplants commits to the tip of another branch. It creates new commits for each one moved over. The benefit is linear history. But be cautious with shared branches to avoid confusing collaborators. Squash Commit Squashing condenses multiple commits into one, streamlining the commit history. Watch the video to see when to use merge vs rebase vs squash when incorporating changes between main and feature branches. – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages):

Git Merge vs. Rebase vs. Squash Commit What are the differences and when should you use each? As I explain in more detail in the video, there are some key distinctions. Git Merge This creates a new commit in the target branch. The new commit ties the histories of both main and feature branches together. Git merge is non-destructive - it introduces a new commit without altering existing ones. Git Rebase Rebase transplants commits to the tip of another branch. It creates new commits for each one moved over. The benefit is linear history. But be cautious with shared branches to avoid confusing collaborators. Squash Commit Squashing condenses multiple commits into one, streamlining the commit history. Watch the video to see when to use merge vs rebase vs squash when incorporating changes between main and feature branches. – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages):

Sahn Lam

65,209 views • 2 years ago

MIT DEDICATED A FULL LECTURE TO GIT'S INTERNALS -- BECAUSE THEY FOUND MOST DEVS MEMORIZE THE COMMANDS AND HAVE NO IDEA WHAT THE TOOL ACTUALLY DOES A whole 85 minutes MIT session that refuses to teach git as a list of commands to copy, and instead shows you the data model underneath -- the thing that makes every command finally make sense. -> The moment it clicks, git stops being scary magic. You stop memorizing "The incantation that fixed it last time" and start actually knowing what's happening. Most people learn just enough git to not get fired. Four commands, blind faith, and a prayer before every merge. In 2026 that's not enough anymore -> git is the literacy test for being in the room, and "I'll just reclone it" is the fastest way to look junior. An AI agent will branch, commit and rebase faster than you can read. When it tangles the history, untangling it runs on understanding the model MIT teaches in this one hour. Anyone can run git push. The person who understands the graph underneath is the one who saves the repo when it breaks. Bookmark & Watch it ↓

MIT DEDICATED A FULL LECTURE TO GIT'S INTERNALS -- BECAUSE THEY FOUND MOST DEVS MEMORIZE THE COMMANDS AND HAVE NO IDEA WHAT THE TOOL ACTUALLY DOES A whole 85 minutes MIT session that refuses to teach git as a list of commands to copy, and instead shows you the data model underneath -- the thing that makes every command finally make sense. -> The moment it clicks, git stops being scary magic. You stop memorizing "The incantation that fixed it last time" and start actually knowing what's happening. Most people learn just enough git to not get fired. Four commands, blind faith, and a prayer before every merge. In 2026 that's not enough anymore -> git is the literacy test for being in the room, and "I'll just reclone it" is the fastest way to look junior. An AI agent will branch, commit and rebase faster than you can read. When it tangles the history, untangling it runs on understanding the model MIT teaches in this one hour. Anyone can run git push. The person who understands the graph underneath is the one who saves the repo when it breaks. Bookmark & Watch it ↓

slash1s

458,408 views • 2 months ago

MICROSOFT PUT THE ENTIRE SOURCE CODE OF WINDOWS INTO A SINGLE GIT REPO -- 300 GIGABYTES, 3.5 MILLION FILES AND MADE IT CLONE IN SECONDS 31 minutes from the Microsoft engineer who actually did it, bending the tool you use for a 50-file side project to hold the biggest codebase on the planet. -> The moment it lands, every excuse dies. You've heard "Git doesn't scale, use something else" your whole career. They ran git status on the largest repo alive and it came back instantly. The secret wasn't a different tool. It was understanding what git actually stores and realizing you never need the whole thing on disk. Pull only the files you touch. Ignore the 3.4 million you never will. Knowing the commands was never the ceiling -> understanding how git stores and moves things is what lets you do what everyone swears is impossible. And as AI agents spin up repos that balloon overnight, knowing how git scales is what keeps you from drowning in your own history. Everyone treats git like it maxes out at a hobby project. One team quietly proved it can hold an operating system. Bookmark & Watch it today ↓

MICROSOFT PUT THE ENTIRE SOURCE CODE OF WINDOWS INTO A SINGLE GIT REPO -- 300 GIGABYTES, 3.5 MILLION FILES AND MADE IT CLONE IN SECONDS 31 minutes from the Microsoft engineer who actually did it, bending the tool you use for a 50-file side project to hold the biggest codebase on the planet. -> The moment it lands, every excuse dies. You've heard "Git doesn't scale, use something else" your whole career. They ran git status on the largest repo alive and it came back instantly. The secret wasn't a different tool. It was understanding what git actually stores and realizing you never need the whole thing on disk. Pull only the files you touch. Ignore the 3.4 million you never will. Knowing the commands was never the ceiling -> understanding how git stores and moves things is what lets you do what everyone swears is impossible. And as AI agents spin up repos that balloon overnight, knowing how git scales is what keeps you from drowning in your own history. Everyone treats git like it maxes out at a hobby project. One team quietly proved it can hold an operating system. Bookmark & Watch it today ↓

slash1s

255,565 views • 2 months ago

Who's winning the global software development race? 🚀 Watch the top 20 economies battle it out in this animated bar chart race of cumulative git pushes since 2020. 📊 This is just one of the new visualizations in our latest GitHub Innovation Graph update. See more trends (including the rise of AI and LLMs) in the full report. 👇

Who's winning the global software development race? 🚀 Watch the top 20 economies battle it out in this animated bar chart race of cumulative git pushes since 2020. 📊 This is just one of the new visualizations in our latest GitHub Innovation Graph update. See more trends (including the rise of AI and LLMs) in the full report. 👇

GitHub

126,580 views • 1 year ago

A DEVELOPER PROVED YOU CAN FIND THE EXACT COMMIT THAT BROKE YOUR CODE IN A HISTORY OF 10,000 -- IN ABOUT 13 STEPS, AUTOMATICALLY.. 33 minutes from a Google engineer on git bisect: the built-in command that binary-searches your entire history to hunt down the one commit that introduced a bug. -> The moment it lands, "When did this break?" stops being an afternoon of guessing. You hand git a good commit, a bad one, and a test and it finds the culprit while you watch. Most people debug a regression by reading diffs by hand, blaming the obvious file, and hoping. Bisect doesn't hope. It cuts the search in half, then in half again, until only the guilty commit is left standing. Reading history by hand was never the skill -> letting git do the binary search for you is. And when an AI agent dumps hundreds of commits into your repo and one quietly breaks production, bisect is what finds the needle without you reading a single line. The bug isn't hiding. It's sitting in one exact commit. Most people just never learned to make git point at it. Bookmark & Watch it today ↓

A DEVELOPER PROVED YOU CAN FIND THE EXACT COMMIT THAT BROKE YOUR CODE IN A HISTORY OF 10,000 -- IN ABOUT 13 STEPS, AUTOMATICALLY.. 33 minutes from a Google engineer on git bisect: the built-in command that binary-searches your entire history to hunt down the one commit that introduced a bug. -> The moment it lands, "When did this break?" stops being an afternoon of guessing. You hand git a good commit, a bad one, and a test and it finds the culprit while you watch. Most people debug a regression by reading diffs by hand, blaming the obvious file, and hoping. Bisect doesn't hope. It cuts the search in half, then in half again, until only the guilty commit is left standing. Reading history by hand was never the skill -> letting git do the binary search for you is. And when an AI agent dumps hundreds of commits into your repo and one quietly breaks production, bisect is what finds the needle without you reading a single line. The bug isn't hiding. It's sitting in one exact commit. Most people just never learned to make git point at it. Bookmark & Watch it today ↓

slash1s

37,773 views • 2 months ago