4 ms·

Could we have this pinned because the whole "Google uses a Monorepo and so should you" has become a huge meme and grown legs. And you're right this topic is on

• tosh 7y ago
  imho the problem space of evolution + stability of systems is becoming more zeitgeisty (more people are aware of the challenges and stumble upon monorepo as a tool to deal with this among other things) related: * unison * clojure (immutability, spec, …) * blockchain * microservice architecture
• cmrdporcupine 7y ago
  I mean honestly, having worked with a monorepo here, I'd definitely consider it for other places. It has advantages.
  • lanstin 7y ago
    The only arguments I have found against monorepo that don’t seem wrong are “the developers aren’t that good at git and can’t handle it.” Other wise it’s just making it harder to find out what code is where.
    • rakoo 7y ago
      Well Google's monorepo is not git, and not even a "standard" one because it's not just a VCS: it's also a storage and a build infra, all in one. So while it's true that many developers wouldn't be comfortable using monorepos in git, it's not the right criticism. The real one is "there is no unified tool to do it correctly". Or at least I don't know of any.