4 ms·

Vanishingly small in number, but quite significant in terms of the number of developers working in them.

• Polylactic_acid 7y ago
  All of the organizations that have outgrown git will have such incredibly specific requirements meaning nothing but a custom built tool will work for them.
  • rumanator 7y ago
    The so called problem would also vanish if the monorepo was modularized and broken up into smaller repos.
    • adrianN 7y ago
      That's probably a harder task for an existing monorepo that is too big for git than writing a replacement for git that works with a repo of that size.
      • rumanator 7y ago
        The problem boils down to refactoring a large monolith. I feel like Git is a scapegoat for a much larger problem.
        • neerajsi 7y ago
          Let's say you started with a well factored set of code that is managed within your organization. What advantage is there to having multiple repos if you're not limited by your tools? Refactoring is easier within a single repo...
          • neoeldex 7y ago
            There probably will be a plethora of different hard issues to fix in such situations. It's also easier to institute change in a dictatorship as opposed to a democracy (being a dictator that is :).
          • adrianN 7y ago
            In my experience, code doesn't stay well factored unless there are technical hurdles that keep it so. That of course doesn't have to be a repo boundary, but in can be.
  • alexhutcheson 7y ago
    Objectively not true. Many (most?) are just using Perforce in an off-the-shelf configuration.