The Real Problems w/ Git

Source code control as a Service. Good idea! Maybe we can make people in India resolve all our merge conflicts and say AI did that.

You can tell how much theprimeagen disagrees by how quiet he is.

I think a lot of people forget when discussing git. it wasn't designed for small teams. it wasn't designed for shipping fast. it was designed for *the linux kernel* , which is why it works so weirdly if you have a central server - it wasn't designed to have a central server, but a central *person* to deal with conflicts

I wish they asked more questions about Casey's VCS. Does it have history? Is it duplicating files? Does it have a concept similar to branches? Are super-positions the whole file or parts of a file? Its an interesting way of looking at the problem, but it sounds like its focused on making sure everyone has up to date files than preventing the loss of source files or being able to go back to old versions of the source.

interesting talk. Linus had said in a talk at Google (YT vid) that Git tracks **content**, not **files**. Game dev has traditionally been more about assets/files, so Git is not a great fit there. However for the Linux kernel, which Git was designed for, Git is a great fit! Another fun fact: CVS was born from some Dutch guy who wrote a throwaway script and shared it online. He only found out years later that many people were using it.

Prime: Why don't you like it? Casey: it insists upon itself

Git specifically was made for a distributed set of distributed teams of thousands of developers in total in a repository that does not have large binary assets. It is still kind of perfect for that.

casey is literally describing syncthing. it keeps files in sync. if a conflict happens, a copy is made then users can merge copies

I'm not surprised that Casey has gone full quantum. On the next standup, he'll be putting lines of code in the large hadron collider to see what happens.

I'm just glad you guys saved those two characters in the title.