3 ms·

I struggle to understand the upside of avoiding monorepos. A lot of people think it means you can't decouple releases, modularize builds and similar with a mono

I struggle to understand the upside of avoiding monorepos. A lot of people think it means you can't decouple releases, modularize builds and similar with a monorepo, but that's simply not true. The efficiency at which you can refactor and upgrade your codebase cannot be understated.

IshKebab 3y ago
The main upsides I see are: * you can pretend you don't need a proper sandboxing build system like Bazel, Buck etc. and stick to Make/CMake etc. * you don't need to learn how to use sparse checkouts It basically lets you avoid learning how to solve the problems you'll inevitably run into for a little while. Not a great reason, but it is a reason.
sethammons 3y ago
every monorepo I've seen suffers from a shit CI solution. Other teams break your builds. Builds get longer and more complex. Feedback loops slow down. Engineering velocity slows down. It works at Google because they spent, literally, hundreds of millions of dollars getting it working.
- knallfrosch 3y ago
  It's not even clear whether a monorepo stretches across teams or not. I think many people are argueing about different things.