Software developers are building a better future and moving our world forward. Software powered innovation is at the heart of breakthroughs and advancements; from smarter homes and healthcare to faster banking and e-commerce, from IoT Innovations to more efficient factories and industrial production. The developer workforce builds products and creates jobs while delivering societal and economic value.
The Developers Alliance serves and supports the workforce that makes this better world possible. We are the world’s leading advocate for software developers and the companies invested in their success. Alliance members include industry leaders in consumer, enterprise, industrial, and emerging software, and a global network of more than 75,000 developers.
Our Mission: Advocate on behalf of developers and the companies that depend on them, support the industry’s continued growth, and promote innovation.
Great talk! It feels great to know how the got to be. Must've been awesome to work at Google during those years. So many great talks. Random recommendation from RU-vid in 2024 at 3 am.
Linus Torvalds: git cannot handle extremely large repositories Narrator: gir could, in fact, handle very large repositories and would be modified to handle the entire windows source tree.
Yes and no. There's no politics around making changes, was his point. If you want to centralise control of your version of a repository, that's fine, and you can still allow others to fork and make whatever changes they think are useful and try to get it merged upstream. Most don't, but that's because of intrinsic network effects, not a limitation of the git model itself.
While git is great and became like the only thing used for SCM its funny to see how he is emphasizing that decentralized repositories are the only thing to go. Actually the problems which reside from it are addressed in his talk but not seen as that big they need fixing. One point is that there is no serious project which isnt hosted on GitHub or anything similar, which is the source of truth. And there has to be beacuse in the end there is one product with one conpiled software. Furthermore bloating up repos without the option the undo the blow-up at a certain point, making things slow again. These "stupid" people with write access push 10GB binaries to the repo and its in there forever and make things incredibly slow again
26:59 pushes Linus to admit that in his decentralized utopia, there's actually a master node and it's Linus' computer. Maybe that's when Preston-Werner realised he should make github.
Compared to a purely centralized system, at least it allows developers to work on their own branches and still have some version tracking, until they push to the central server. But in the end, most people pretty much use git as a centralized system. I've seen many companies use it this way - mainly to track developers' work on a daily basis, rather than make their life easier. It's often used as a micro-management tool.
Only from this talk I realized you can pull from each other with git, pretty dope on paper, but yeah seems like most projects default to having a central server.
@@orlagh277 Well yes, as a distributed system, that's one of the points. Now very few actually do that. Most people seem to be using git as SVN, only pretending they use a modern tool with all the hype, to look cool. The fun part is that even Linus doesn't use git as most other people do, and the "typical" github workflows (github is not git, but github has become the defacto "tool" for many too, and that influences the way they see and use git) have nothing to do with how the Linux Kernel is managed.
Yes, the project he made uses his computer as a master node because most people agree on that. If everybody decided to send their patches to someone else and distros stopped using the main upstream, the master node practically wouldn't be him anymore.
Imagine having a flaky internet connection, because you're on the move. It's now super hard to commit because you're not committing locally. You're committing to a central server, so now you're either spamming the commit button in the hope it'll go through or you're stuck not being able to do anything at all.
Want to send a patch? Go through the server. Want to share a branch? Go through the server. Server is down? You're now fucked. Git has none of these problems, because it's distributed.
No. CVS and SVN are rather similar from a user perspective. Git is the odd man out. Git is overly complicated in practice, though it's fine as a local revision control system. It gets real crazy when using it remotely with a load of feature branches... which seems to be how many people use it.
@@NostraDavid2Git has the same problems when the server is down, or if the network connection is lost. How would you share a Git branch without a connect to the "server" or whatever you want to call it? I work from home. If I lose connection, I lose access to the central repo.
Today git didn't cope to the hype, just overused, like jira, like react, just use something but don't know why. When git can merge code from multiple developers from different pcs and work on zero day production, like DOOM than we can talk.
It sounds like either you don't know what you're saying or you haven't taken your meds. Or both. Git can merge from different devs, wtf is "zero day production" and DOOM is like 30 years old
And now git is a gigantic standard across so many companies. Imagine starting not 1, but 2 major software projects in your life that end up being used by millions daily
@@MrEnsiferum77 Usually better, indeed. People used to sit together for interactive merging sessions (which doubled as code reviews), instead of using a tool that will auto-merge stuff in a lot of cases, breaking horribly, or not being able to merge and letting you take care of that yourself until, uh, it breaks too. I find Mercurial a better tool. But that's similar - it shouldn't be used as a replacement for brains.
SVN. Git is better, but it's not like there was nothing, and then suddenly on the 8th day, God spoke and there was git. It's an iteration on other verson control concepts
@@Jabberwockybird Yes of course, and as I mentioned Mercurial, it's definitely not the first distributed one either. Linus wrote it to fit his own particular needs for maintaining the Linux kernel, and that appears to work quite well in that context, alhough, paradoxically, he uses it in ways that are quite different from what most people do with git these days.
No it's not, u have plenty of proto blockchain systems, or decentralized banking systems before git is just hype for liberal developers, maybe just make sense in linux kernel world. Using it everywhere today, doesn't mean u need it.
