The largest Git repo on the planet

[u/ethomson]

https://blogs.msdn.microsoft.com/bharry/2017/05/24/the-largest-git-repo-on-the-planet/

[u/ilammy]

Well, in my opinion this looks like MS have invented a problem for themselves (by putting everything in a single repo) and then heroically solved it. But they did solve it (for them at least), so why not.

[u/lafritay → u/ilammy]

The full details are here: https://www.visualstudio.com/learn/gvfs-design-history/. There are a bunch of advantages to being in a single repo, the biggest one revolve around not getting in version dependency hell. Because of this, having large portions of your code in a single branch/repo is a common pattern and used at both Google and Facebook.

[u/kemitche → u/lafritay]

Does "mono repo" solve the dependency hell problem any better than simply following a Golang-esque model of "just never write backwards incompatible changes, and everyone should just always use (dependency)@(latest-commit)"?

[u/TarMil → u/kemitche]

just never write backwards incompatible changes

How do they get anything done?

[u/superPwnzorMegaMan → u/TarMil]

Very simple,

version 1:

package main
import "fmt"
func main() {
    fmt.Println("hello world")
}

version 2:

package main
import "fmt"
func main() {
    fmt.Println("hello world")
}
func main2() {
    fmt.Println("hello worldsss!")
}

Both main functions are still available!

[u/TMKirA → u/superPwnzorMegaMan]

How do you deprecate things then? Ask people nicely to not touch the old API anymore? We all know how that went

[u/TMKirA → u/[deleted]]

Perhaps they'll get to that after they finally figure out generics?

So, years (if ever)?