He notes that these repositories are somewhat broken up already, and wants to keep them together. There are good reasons to keep code in one repository; partic

He notes that these repositories are somewhat broken up already, and wants to keep them together. There are good reasons to keep code in one repository; particularly, git's submodule support has a number of nasty interface tradeoffs; I wouldn't say it breaks git, but you have to keep a clear understanding of all your submodules in your head when you have a lot of them. OK, it pretty much breaks git to have submodules that are interdependent. I know this because I am currently moving one of my organizations off this exact plan -- it's the opposite of useful and speedy to have to worry about versions across a large number of backend / frontend repositories. It is MUCH easier and therefore better for developers to put them together, and release together.