It seems we agree, we are both claiming that "there is no one right way". I love Git, and I used submodules for years in personal projects. It started with a

It seems we agree, we are both claiming that "there is no one right way". I love Git, and I used submodules for years in personal projects. It started with a few support libraries shared between projects, or common scripts for deployment, but it quickly ballooned into a mess. I'm in the process of moving related personal projects to a monolithic repository, and in the process I'm giving up the ability to tag versions of individual projects or provide simple GitHub links to share my code. Based on these experiences, I honestly think that the only major problem with monolithic repositories is that the software isn't good at handling it, and this problem could be solved with better software. If the problem is solved at some point in the future, I don't think the answer will look much like any of the existing VCSs. Based on experiences in industry, my observation is that the choice of monolithic repository versus separate repository is highly specific to the organization.