Comments by "Lawrence D’Oliveiro" (@lawrencedoliveiro9104) on "Teamwork u0026 Git - Computerphile" video.

Maybe that’s an argument for using names rather than numbers.
5
@menachemsalomon I don’t understand the point of that. It’s just a recipe for needless obfuscation -- and trouble, as you discovered.
5
@djp_video I have never heard of these sorts of problems from any other user of Git. It has a reputation for rock-solidity. Remember how it became popular: it did not have the backing of any big company, no management mandating its use, only a small cadre of smart open-source developers who used it to gain a quantum leap in productivity. No slick, multi-million-dollar advertising campaign: only the first-hand testimony of real users. And its adoption grew from there. But this is all beside the point. If it pains you so much, why do you insist on using it? Maybe you would be better off with something like Microsoft Team Foundation Server. Then at least you can blame Microsoft for your problems.
4
Warning: Using TFS or Visual SourceSafe can be seriously harmful to your programmers’ productivity.
3
You should ask yourself: is your project as large and complex as the Linux kernel? Over 20 million lines of code, thousands of new and changed code flowing in each day from over a thousand active contributors, with a new major, stable release coming out about every three months. And they manage it all with Git. I’m guessing that your particular project is a lot smaller than that. So if they can be so productive with Git, and you cannot, guess where I suspect the problem lies?
3
pid content tracker”. He wouldn’t trust his code to the elaborate conflict-resolution schemes that some people were coming up with .So Git provides the tools to narrow things down to just the relevant places needing fixing up, with a minimum of irrelevant detail, and leaves you to sort it out.
3
Bitbucket started out as an online repo service only for Mercurial. It got forced into providing Git as an alternative, by popular demand. And then the popularity of Mercurial diminished to the point where it wasn’t worth supporting any more. So that is now gone.
3
@flyball1788 You don’t just want to be able to diff(1) them you also want to be able to patch(1) them and be able to do merges on them. If you have a tool that can convert them to/from a text format, why not store that text format in the repo, and convert it to binary as part of the build process?
3
@zxuiji The problem with locking is it slows down development and makes things awkward, like when you find that somebody has locked something they didn’t need to, and you have to ask them to unlock it so you can work on it. That’s why locking was done away with. That’s why productivity is so much greater with modern VCSes than those older, locking-based ones.
2
I can’t even see anything in standard SQL that allows columns to be referenced by numbers, only names. Not in the SQL 2003 spec, anyway.
2
beta, eta, theta, zeta ... they all rhyme.
2
Conflict resolution is one area where Git is a major advance on what came before. Linus Torvalds himself describes Git as the “stu
2
Certainly text files are preferable to binary. A key point about version control is about being to diff two different states of the tree to see what has changed. With a text file, you can see changes line by line; with a binary file, you can’t.
2
File locking is how version control used to work back in the 1980s. Because it was thought that, if two people simultaneously made changes to the same file, the world would end or something.
1
With Git, it’s “commit early and often”. 😎
1
Are you trying to use it on Microsoft Windows, by any chance?
1